Dependency mapping in a database environment

US10789208B2 · kind B2 · utility

Assignee

• SAP SE · DE

Inventors

• Jonathan Bregler · Gondelsheim, DE
• Alexander Bunte · Heidelberg, DE
• Arne Harren · Walldorf, DE
• Andreas Kellner · Birkenau, DE
• Daniel Kuntze · Bruchsal, DE
• Simon Lueders · Walldorf, DE
• Volker Sauermann · Dossenheim, DE
• Michael Schnaubelt · Walldorf, DE
• Le-Huan Stefan Tran · Malsch, DE

Key dates

• Filing date: Aug 2, 2017
• Grant date: Sep 29, 2020
• Expiry date: Feb 2, 2038

Classification

• Technology area (CPC G): Physics
• CPC primary: G06F16/9017
• WIPO field: Computer technology
• WIPO sector: Electrical engineering

Abstract

Embodiments map from a database environment, dependencies between files created at designtime and corresponding runtime data objects defined by deployment of those files. A dependency table is populated with dependency information (e.g., origin, target, dependency type) extracted during deployment. That dependency information may be searched according to user-specified parameters (e.g., a file provides an object; an object requires a file), to allow rapid correlation between designtime file(s) and related runtime data object(s). Embodiments are particularly useful in visualizing complex (e.g., one-to-many; many-to-one) file-object dependencies characteristic of modern database environments. Queries posed to the dependency table may further seek intra-designtime dependency information (e.g., one file depends upon another file; one file impacts another file), and/or intra-runtime dependency information (e.g., table objects referenced by view objects; view objects referenced by procedure objects). Dependency information may be recursively searched in an iterative manner in order to construct dependency pathways reflecting complex file-object relationships.