Database Metadata Validation for Broken Query Visualizations

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Database metadata changes, such as column additions, deletions, or renames, cause mismatches between the database metadata and the query model, leading to failed queries and broken visualizations in dashboard applications, which are difficult for end-users to diagnose and rectify.

Innovation Solution

A metadata update and validation mechanism that includes a guided query validation tool, allowing users to update and rectify metadata mismatches by selecting columns for use in visualizations, presenting errors, and enabling users to delete or replace columns to ensure accurate queries and visualizations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If database metadata is updated automatically, then the query model becomes outdated and causes query failures, but if manual updates are required, then user workload and time consumption increase

Engineering Contradiction:
Improvequery execution reliabilityVSAvoiduser time for metadata maintenance
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary validation by comparing database metadata with query model metadata before query execution. This early detection prevents query failures by identifying mismatches in advance, allowing the system to prompt users for updates before the actual query runs, thus maintaining reliability while minimizing user intervention time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where validation results are communicated to users through a user interface. When metadata mismatches are detected, the system provides specific error information and guides users through the update process, enabling efficient correction without requiring users to understand the underlying technical details.

Inventive Principle:
Principle #23Feedback

2Measurement precision

If comprehensive metadata validation is performed, then query accuracy improves, but system complexity and processing time increase

Engineering Contradiction:
Improvemetadata validation accuracyVSAvoidvalidation system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The validation system is segmented into distinct components: metadata comparison module, error detection module, and user guidance module. Each component handles a specific aspect of validation, making the overall complex system manageable and maintainable while achieving comprehensive validation coverage through modular organization.

Inventive Principle:
Principle #1Segmentation

3Ease of repair

If detailed error information is provided to users, then ease of rectification improves, but information overload and user confusion may occur

Engineering Contradiction:
Improvemetadata error rectification easeVSAvoiduser interface simplicity
Core Design Contradiction:
Ease of repairVSEase of operation

Solution Approach 1:

The system applies local quality by providing detailed error information specifically at the location where it is needed - in the user interface elements directly related to the erroneous query. Error messages are contextualized to show exactly which metadata fields have mismatches and how to fix them, without overwhelming users with unrelated system-wide information.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12423275B2Database metadata update validation
Publication Date: 2025.09.23 SAP SE
  • US12423275B2 patent drawing
  • US12423275B2 patent drawing
  • US12423275B2 patent drawing

AI summary

A user interface may include one or more visualizations based on queries to a database using query model metadata. Updated metadata of columns of the database may be obtained which may be different from the query model metadata. A set of used columns and a set of unused columns may be determined based on the query model. One or more metadata mismatches may be determined based on a comparison of the query model metadata for the set of used columns and the updated metadata for the set of used columns. The one or more metadata mismatches may be presented in a user interface configured to enable a user to rectify each. One or more selections from the user may be obtained to rectify at least one of the one or more metadata mismatches. The corresponding columns may be deleted or replaced based on the one or more selections.