Predicting Index Fragmentation via SVM Regression Models

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Index fragmentation in databases leads to inefficient SQL query execution, requiring manual detection by database administrators, which is time-consuming and can result in inefficient database access, especially when fragmentation is significant, necessitating either online defragmentation or offline rebuilding, both of which have performance impacts.

Innovation Solution

A predictive regression model, such as a support vector machine, is used to estimate the change in average index fragmentation percentage for affected indexes, allowing for the determination of total predicted index fragmentation caused by an SQL statement, enabling developers and DBAs to schedule operations to minimize fragmentation and optimize index maintenance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual checking of index fragmentation by database administrators is performed, then fragmented indexes can be identified, but the process is time-consuming and tedious

Engineering Contradiction:
Improveindex fragmentation detection accuracyVSAvoidtime for manual fragmentation checking
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system enables automatic detection and prediction of index fragmentation without requiring manual intervention from database administrators. The predictive regression model automatically analyzes SQL statements and estimates their impact on index fragmentation, allowing the system to self-monitor and self-report fragmentation issues.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical manual process of checking index fragmentation with an automated computational system using predictive regression models. The system substitutes human DBA efforts with machine learning algorithms that automatically predict fragmentation levels based on SQL statement analysis.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If index defragmentation is performed online while the index remains available, then database access efficiency is maintained, but the process is complex and may still impact performance

Engineering Contradiction:
Improvedatabase access availabilityVSAvoidcomplexity of online defragmentation process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary analysis of SQL statements to predict index fragmentation before it occurs. By estimating the fragmentation impact of upcoming operations, the system can proactively schedule maintenance activities or adjust indexing strategies in advance, preventing severe fragmentation rather than reacting to it.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The predictive regression model provides continuous feedback about expected fragmentation levels resulting from SQL operations. This feedback loop allows database administrators to make informed decisions about when to perform maintenance and which indexes require attention, creating a responsive system that adapts to changing database conditions.

Inventive Principle:
Principle #23Feedback

3Reliability

If index rebuilding is performed offline to resolve significant fragmentation, then index performance is restored, but the index becomes unavailable during the rebuild process

Engineering Contradiction:
Improveindex performance efficiencyVSAvoiddatabase query execution speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary prediction of fragmentation caused by SQL statements, allowing proactive scheduling of index maintenance during appropriate maintenance windows rather than forcing unplanned offline rebuilds that disrupt productivity. This enables performance optimization without unexpected service interruptions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a dynamic approach where the system continuously monitors and predicts fragmentation levels, allowing flexible decision-making about when to perform online defragmentation versus when to schedule offline rebuilds. This dynamic system adapts to current database conditions and workload patterns to minimize impact on productivity.

Inventive Principle:
Principle #15Dynamics

4Productivity

If frequent index maintenance is performed to prevent fragmentation, then query efficiency is maintained, but the maintenance operations consume additional system resources and time

Engineering Contradiction:
ImproveSQL query execution efficiencyVSAvoidtime for index maintenance operations
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The predictive regression model estimates fragmentation impact for individual SQL statements, allowing selective maintenance only when necessary. Rather than performing maintenance on all indexes uniformly, the system applies partial action only to indexes predicted to become fragmented, reducing unnecessary maintenance overhead while still preventing performance degradation.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system changes the parameter of maintenance frequency from fixed/scheduled to dynamic/predictive. By using regression models to predict fragmentation based on SQL statement characteristics, the system adjusts maintenance timing and intensity based on actual needs rather than following a rigid schedule, optimizing the balance between query efficiency and maintenance overhead.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10552399B2Predicting index fragmentation caused by database statements
Publication Date: 2020.02.04 QUEST SOFTWARE INC
  • US10552399B2 patent drawing
  • US10552399B2 patent drawing
  • US10552399B2 patent drawing

AI summary

Systems and techniques for determining a total predicted index fragmentation associated with executing a structured query language statement are described. An execution plan associated with the structured query language statement may be determined. A plurality of tables estimated to be affected by execution of the structured query language statement may be determined. For individual tables, an estimated number of rows that the structured query language statement is to affect may be determined. A predictive model, such as a support vector machine, may be used to determine, for individual tables whose indexes are estimated to be affected, a predicted change in an average index fragmentation percentage associated with individual indexes on the affected tables. The sum of the predicted change in the average index fragmentation percentage of affected indexes may be determined to determine the total predicted index fragmentation associated with executing the structured query language statement.