Metadata-Driven Database Management for Constraint-Based Activity Scheduling

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional database management techniques lack direct administration by development teams, leading to unanticipated database activities causing production failures and lack of visibility and control, resulting in unscheduled and unlogged maintenance.

Innovation Solution

A metadata-driven framework for database management as a service that enables direct administration of database activities by parsing configuration files to identify constraints, configuring parameters, and automatically initiating database procedures based on these constraints, with tracking and reporting of actions and health monitoring.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional database management techniques are used, then database activities are managed independently of database objects, but this leads to production job failures when unanticipated database activities are unexpectedly initiated

Engineering Contradiction:

Improveproduction job stabilityVSAvoiddatabase activity control

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent implements feedback mechanisms by logging all database activities and their outcomes, tracking which applications are affected by each database activity. This feedback loop enables the system to learn from past activities and predict potential conflicts, allowing development teams to adjust constraints and prevent production failures before they occur.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system enables development teams to directly administer their own database objects by defining constraints and schedules for database activities associated with their applications. This self-service capability allows teams to control and protect their own database objects without relying on external database administrators, improving both reliability and ease of operation.

Inventive Principle:

Principle #25Self-service

2Loss of information

If database related activities are scheduled for a set time and independently initiated, then maintenance can be performed, but there is no logging or failure tracking because functionalities, usages, and operational windows are not shared

Engineering Contradiction:

Improvevisibility of database activitiesVSAvoidmanagement system complexity

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The patent creates a universal metadata-driven framework that serves multiple functions: scheduling database activities, logging activities and failures, tracking application dependencies, and providing visibility to development teams. This multi-functional system eliminates the need for separate management tools and processes, reducing overall complexity while improving information visibility.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces a metadata-driven intermediary layer between database objects and development teams. This intermediary framework translates high-level constraints defined by development teams into specific database activity schedules and enforcement rules, while also providing logging and tracking capabilities. The metadata framework acts as a mediator that simplifies complexity by abstracting detailed management operations.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If development teams want direct administration of database objects, then control and visibility improve, but this requires sharing functionalities, usages, and operational windows across management processes

Engineering Contradiction:

Improvedirect administration capabilityVSAvoidmetadata framework complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent enables direct administration by allowing development teams to define and modify parameters such as constraints, schedules, and operational windows for their database objects. These parameter changes are captured in metadata that drives the behavior of database activities. The system adapts to different team requirements by allowing flexible parameter definition without requiring complex structural changes to the underlying framework.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS12393556B2Method and system for providing database management as a service

Publication Date: 2025.08.19 JPMORGAN CHASE BANK NA

AI summary

A method for providing database management as a service is disclosed. The method includes onboarding applications to access a corresponding configuration file; parsing the configuration file to identify constraints that govern a database activity for each of the applications and a database that correspond to each of the applications; identifying database procedures based on the constraints; configuring parameters of the database based on the constraints, the parameters corresponding to the database activity; and automatically initiating, by using the identified database procedures, the database activity for each of the applications based on the configured corresponding parameters.