Centralized Data Access Tool for SQL Resource Governance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Insurance database servers face challenges in managing resource usage during SQL script execution, leading to potential crashes or slow performance, which can result in significant monetary losses due to downtime and impact the retrieval of vital data for insurer employees.

Innovation Solution

A Centralized Data Access Tool (CDAT) is implemented to dynamically control resource limits, optimize SQL scripts, and scrub confidential data, ensuring efficient execution and secure access while preventing resource exhaustion and data breaches.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the server executes SQL scripts to retrieve data, then data access for insurer employees is enabled, but server performance deteriorates and crashes may occur due to excessive processing resources

Engineering Contradiction:
Improvedata retrieval capabilityVSAvoidserver stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by validating and optimizing SQL scripts before execution. The centralized data access tool checks script syntax, potential performance impacts, and resource requirements in advance, preventing problematic scripts from consuming excessive resources and causing server crashes

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A centralized data access tool is introduced as an intermediary between users and the database. This tool acts as a mediator that validates, optimizes, and monitors SQL script execution, controlling resource consumption while enabling data access functionality

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If ad-hoc SQL scripts are executed without resource limits, then data retrieval flexibility is maintained, but server resources are exhausted leading to downtime

Engineering Contradiction:
Improvequery flexibilityVSAvoidserver downtime
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system implements dynamic resource management by adjusting execution parameters and resource allocation based on real-time conditions. The centralized data access tool dynamically monitors resource consumption and adapts script execution parameters to prevent resource exhaustion while maintaining query flexibility

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system incorporates feedback mechanisms where the centralized data access tool continuously monitors SQL script execution resource consumption and provides feedback to control and optimize execution, preventing resource exhaustion and associated downtime

Inventive Principle:
Principle #23Feedback

3Speed

If SQL scripts are optimized for performance, then execution speed improves, but resource consumption increases for critical operations

Engineering Contradiction:
Improvequery execution speedVSAvoidprocessor resource consumption
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The system changes execution parameters dynamically based on the specific SQL script and data requirements. The centralized data access tool adjusts parameters such as execution timing, resource allocation, and optimization levels to balance performance gains with resource consumption for each individual query

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11169997B1Centralized data access tool implementing resource governance
Publication Date: 2021.11.09 STATE FARM MUTAL AUTOMOBILE INSURANCE COMPANY
  • US11169997B1 patent drawing
  • US11169997B1 patent drawing
  • US11169997B1 patent drawing

AI summary

Methods, systems, apparatus, and non-transitory media are described for governing resources used to execute and retrieve database entries in accordance with an ad-hoc structured query language (SQL) script. Various aspects are described to determine whether a written SQL script is optimized, to execute the SQL script if it is optimized, and to otherwise reject unoptimized SQL scripts. The resources used during the execution of the SQL script may further be monitored to control resource use, and the execution of SQL scripts may be ceased if a processor-based resource limit threshold is exceeded. The SQL script execution system may be implemented in a wide variety of systems, such as database servers. The scripts may be executed in conjunction with scrubbing and encryption scripts to protect sensitive data, and thus the SQL scripts may be received via one or more public APIs.