Database Complexity Scoring Using Metadata Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Evaluating the complexity of databases is subjective and varies between evaluators, leading to inefficient resource allocation and inaccurate task evaluations, as the complexity is not objectively measurable.

Innovation Solution

A database complexity score is determined using metadata, incorporating factors like the number of tables, attributes, relationships, and records, with weighted functions and summations to provide an objective measure, and a reduced complexity score can be calculated using logarithmic or square root functions for easier interpretation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If subjective evaluation based on past experience and judgment is used to assess database complexity, then evaluation can be performed without complex calculations, but the evaluation results vary between different evaluators and lack objectivity

Engineering Contradiction:
Improveease of evaluationVSAvoidobjectivity of complexity assessment
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

The patent transforms the subjective evaluation process into an objective one by changing the parameters from qualitative judgments to quantitative measurements. It defines specific measurable parameters including number of tables, number of attributes per table, number of relationships, and number of records. These parameters are then combined using a weighted function to produce a standardized complexity score, eliminating evaluator subjectivity while maintaining ease of assessment.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If total database size in memory is used to evaluate complexity, then the evaluation is simple and straightforward, but it does not reflect the actual structural complexity of the database

Engineering Contradiction:
Improvesimplicity of evaluationVSAvoidstructural complexity information
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent segments the database into its fundamental structural components: tables, attributes, relationships, and records. Instead of treating the database as a single monolithic entity measured by total size, it breaks down the complexity assessment into discrete measurable elements. Each component is quantified separately and then aggregated through a weighted function, preserving the structural complexity information that would be lost in a simple size-based measurement.

Inventive Principle:
Principle #1Segmentation

3Productivity

If no standardized scoring system is used for database complexity, then evaluation can be performed quickly without complex calculations, but resource allocation and task evaluation become inaccurate

Engineering Contradiction:
Improvespeed of evaluationVSAvoidaccuracy of resource allocation
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

The patent replaces the mechanical system of manual subjective judgment with an automated computational system. A standardized scoring function is implemented that automatically calculates complexity scores by retrieving metadata, identifying database information, and applying the weighted function. This substitution maintains high evaluation speed through automation while dramatically improving accuracy and consistency in resource allocation decisions.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS8001158B2Systems and processes for evaluating database complexities
Publication Date: 2011.08.16 HEWLETT PACKARD ENTERPRISE DEV LP
  • US8001158B2 patent drawing
  • US8001158B2 patent drawing
  • US8001158B2 patent drawing

AI summary

A database may be evaluated to determine the complexity of the database. Metadata associated with a database may be retrieved and database information may be identified from the retrieved metadata. Database information may include, for example, a number of tables, a number of attributes of a table, a number of relationships in a table, or a number of records in a table of a database. A database complexity score may be determined based on identified database information.