Database Trace Analysis for Architecture Issue Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database management systems lack effective, automated tools for identifying poorly architected database applications and interfacing issues, which can significantly impact performance and scalability, particularly for non-expert developers.

Innovation Solution

A system that captures and analyzes trace information to detect potential architecture and interfacing issues in database applications, such as multiple connections blocking on the same row and client-side joins, by using a tracing module to record database interactions and a trace analyzing module to generate reports with suggestions for improvement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Difficulty of detecting and measuring

If automated tools are introduced to detect database application architecture issues, then detection capability is improved, but system complexity increases

Engineering Contradiction:
Improvedetection capabilityVSAvoidsystem complexity
Core Design Contradiction:
Difficulty of detecting and measuringVSDevice complexity

Solution Approach 1:

The patent introduces a trace analyzing module as an intermediary component that sits between the database management system and the application. This module captures trace information from database interactions and automatically analyzes it to detect architecture issues such as client-side joins and multiple connections blocking on the same row. By using this intermediary analyzer, the system improves detection capability without requiring direct modification of the database core or application code, thus managing system complexity through a dedicated analysis layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If comprehensive trace information is collected and analyzed, then detection accuracy is improved, but processing overhead increases

Engineering Contradiction:
Improvedetection accuracyVSAvoidprocessing overhead
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by capturing and storing trace information during normal database operations before analysis is needed. The trace analyzing module has access to pre-captured trace data that includes database interactions, connections, and queries. This allows the system to analyze architecture issues without adding significant processing overhead during critical operations, as the trace data is already collected and organized for analysis.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent extracts only the specific trace information relevant to detecting architecture issues such as connection patterns, query structures, and locking behaviors. Rather than analyzing all possible database operations, the system focuses on extracting and analyzing only those trace elements that indicate potential problems like client-side joins or connection blocking patterns. This selective extraction improves detection accuracy while minimizing processing overhead by avoiding analysis of irrelevant data.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8260761B2Detecting performance degrading design and algorithm issues in database applications
Publication Date: 2012.09.04 IANYWHERE SOLUTIONS INC
  • US8260761B2 patent drawing
  • US8260761B2 patent drawing
  • US8260761B2 patent drawing

AI summary

Systems, methods and computer program products for detecting potential architecture and interfacing issues in database applications are described herein. In an embodiment, the invention operates by accessing trace information. The trace information includes database-related information pertaining to interactions of a database application with a production database. The invention detects potential architecture and interfacing issues in the database application by analyzing the trace information. Such architecture and interfacing issues include, but are not limited to, multiple connections simultaneously blocking on the same row of a table, and client-side joins.