Platform-Independent Metadata Catalog Framework
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database systems face challenges in managing and communicating large volumes of metadata across multiple systems in a platform-independent manner, leading to complexity and inefficiency in data replication and recovery processes.
Innovation Solution
The development of a platform-independent metadata catalog framework and logical logging system using JSON objects to represent metadata changes, allowing for efficient data exchange and version management across different database systems, enabling human-readable and machine-parseable metadata logs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If traditional metadata management systems are used to handle large volumes of metadata across multiple database systems, then metadata can be stored and retrieved, but the complexity of managing and communicating metadata increases significantly and platform independence is lost
Solution Approach 1:
The patent implements a universal metadata catalog framework that can store and manage multiple types of metadata objects (tables, views, indexes, procedures, etc.) across different database platforms using a single standardized interface. The catalog uses platform-independent data structures and versioning mechanisms that work uniformly across various database systems, eliminating the need for platform-specific metadata management code and reducing overall system complexity while handling large volumes of metadata.
Solution Approach 2:
The patent introduces version numbers as a key parameter to track metadata object evolution. Each metadata object in the catalog is associated with a version number that enables the system to manage changes over time. This parameter change approach allows the system to handle large volumes of metadata by organizing them into versioned entries, making retrieval and comparison operations more efficient and reducing management complexity.
2Productivity
If platform-specific metadata formats are used for data replication and recovery, then metadata can be communicated between systems, but additional transformations are required and portability is reduced
Solution Approach 1:
The patent introduces a metadata catalog as an intermediary layer between different database systems. The catalog stores metadata in a standardized, platform-independent format that acts as a mediator, allowing metadata to be exchanged between heterogeneous database systems without requiring direct platform-specific transformations. This intermediary approach improves data exchange efficiency while maintaining full platform independence and adaptability across different database vendors and versions.
3Reliability
If metadata versioning is implemented to track changes across database systems, then metadata evolution can be managed, but the structure and management of the metadata catalog becomes more complex
Solution Approach 1:
The patent implements preliminary versioning by assigning version numbers to metadata objects before they are stored in the catalog. This preliminary action allows the system to pre-organize metadata into versioned entries, making subsequent change tracking and retrieval operations simpler and more reliable. The version number is established upfront, reducing the complexity of managing metadata evolution while ensuring accurate version tracking across database systems.
Data Source
AI summary
Systems and methods for generating a platform-independent metadata catalog framework of a database system are disclosed. These include receiving, at the database system, a metadata object, and determining a version of the received metadata object. Responsive to determining that a metadata catalog, which has catalog entries associated with unique versions of metadata objects, does not include a catalog entry associated with the version of the received metadata object, a catalog entry in the metadata catalog is created. The created catalog entry is then associated with the version of the received metadata object. Furthermore, a version number based on the version of the received metadata is generated, which is associated with the created catalog entry. Related apparatus, systems, techniques and articles are also described.