Centralized Stored Procedure Management with Version Tracking

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Large entities face challenges in implementing and enforcing standards across different development teams, leading to difficulties in tracking and managing stored procedures, including version control and compliance with entity standards.

Innovation Solution

A system that stores all stored procedures in a central location, generates change identifiers for each version, validates them against entity standards, and tracks modifications and locations, allowing for efficient management and compliance checking.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If development teams store stored procedures in team-specific systems with team-specific naming conventions, then each team can work independently, but it becomes difficult to track progress, locate stored procedures, and distinguish between different versions

Engineering Contradiction:

Improveindependent team operationVSAvoidtracking and location information

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent merges multiple team-specific stored procedure repositories into a single centralized repository. This consolidation allows all development teams to store their stored procedures in one location, enabling unified tracking, version control, and location identification while preserving team independence through standardized access mechanisms

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent implements a universal naming convention and tracking system that serves all development teams regardless of their specific divisions. This universal approach enables the centralized repository to handle stored procedures from multiple teams with consistent identification, versioning, and location tracking capabilities

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If multiple development teams use different naming conventions and store procedures in separate systems, then team autonomy is maintained, but entity-wide standards cannot be enforced

Engineering Contradiction:

Improveteam autonomyVSAvoidcompliance with entity standards

Core Design Contradiction:

Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The patent establishes entity-wide naming conventions and standards before development teams create stored procedures. The centralized repository is configured with predefined rules and validation mechanisms that automatically enforce these standards during the storage process, preventing non-compliant stored procedures from being saved while allowing teams to work autonomously

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements an automated validation system that provides immediate feedback to development teams when they attempt to store non-compliant stored procedures. The system checks each stored procedure against entity standards and returns specific error messages indicating what corrections are needed, enabling teams to self-correct while maintaining standard compliance

Inventive Principle:

Principle #23Feedback

3Manufacturing precision

If stored procedures are stored in a centralized location with validation against entity standards, then compliance is ensured, but the system complexity increases

Engineering Contradiction:

Improvecompliance with entity standardsVSAvoidsystem structure

Core Design Contradiction:

Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent implements automated validation mechanisms that perform compliance checking without requiring manual intervention from system administrators. The centralized repository automatically validates each stored procedure against entity standards using pre-configured rules, generating change identifiers and version information automatically, thereby reducing the operational complexity despite the centralized structure

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS9658848B2Stored procedure development and deployment

Publication Date: 2017.05.23 BANK OF AMERICA CORP

AI summary

Methods, systems, and computer-readable media for developing, storing, validating, tracking and transferring stored procedures are presented. The stored procedures may be stored in a central storage location. The storage location may receive a first version of a stored procedure and generate a change identifier for the first version. The system may evaluate the stored procedure to determine whether it complies with standards of the entity. In some examples, the first version may be checked-out and transferred to another environment for, for instance, modification to create a second version. The second version may then be transmitted to the central storage location for storage. A second change identifier may be generated and associate with the second version. The second version and the second change identifier may be stored. Similarly, an unlimited number of modifications to the stored procedure, each associated with a unique change identifier from the storage system, may be made.