Uniform Metadata Retrieval Interface for Relational Databases

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current database searching applications, such as SQL, require users to write complex queries to retrieve metadata, which is time-consuming and expensive, especially when dealing with different relational database organizations.

Innovation Solution

A method for uniform metadata retrieval is introduced, which generates an interface for requesting metadata from a relational database, translating hierarchical metadata requests into relational database queries to improve ease of querying and predictability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional database searching applications like SQL are used to retrieve metadata, then the metadata can be retrieved from the relational database, but the process requires writing complicated select statements which is time-consuming and expensive

Engineering Contradiction:

Improvemetadata retrieval capabilityVSAvoidtime to write complex queries

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces an intermediary layer (metadata service or abstraction layer) that sits between the user and the relational database. This intermediary automatically generates the complex SQL select statements based on simpler metadata requests, eliminating the need for users to manually write complicated queries while still retrieving the required metadata from the database

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

Engineering Contradiction:

Improvemetadata retrieval capabilityVSAvoidease of querying

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

The intermediary layer provides automated query generation that abstracts away the complexity of SQL syntax and database schema details. Users simply specify what metadata they need through a simplified interface, and the intermediary handles the complexity of translating this into proper SQL queries, eliminating the need to consult product documentation

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service by automatically generating the appropriate select statements without requiring user expertise in SQL or database structure. The intermediary service autonomously handles query construction, optimization, and execution based on the user's simple metadata request

Inventive Principle:

Principle #25Self-service

3Reliability

If the same querying process is repeated for different relational databases with different relational organizations, then metadata can be retrieved from each database, but the process must be repeated and is inefficient

Engineering Contradiction:

Improvemetadata retrieval capabilityVSAvoidquerying efficiency across databases

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent creates a universal metadata service that can handle queries across multiple relational databases with different organizational structures. The intermediary layer maintains an understanding of various database schemas and automatically adapts the query generation process to work with different database organizations, allowing a single querying process to efficiently retrieve metadata from multiple databases

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS7693911B2Uniform metadata retrieval

Publication Date: 2010.04.06 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

A method for uniform metadata retrieval generates an interface for requesting metadata from a relational database. A hierarchical metadata request can be received via the interface. The hierarchical metadata request can be translated into a relational database metadata request. The relational database metadata request is utilized to retrieve metadata from the relational database.