Database Modification Execution Time Estimation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database users and application developers face challenges in estimating the execution properties of database modification statements, such as execution time, due to the lack of clear methods for determining operational size and throughput rate.
Innovation Solution
A computer-implemented method that identifies database modification statements, generates operational unit indicators, determines anticipated operational size and throughput rate, and calculates the anticipated total execution time based on these metrics, using statistical information and operational records from the database management system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional database modification statements are executed without estimation methods, then the database operations can be performed, but the execution time and operational size cannot be accurately predicted
Solution Approach 1:
The system performs preliminary analysis by identifying operational unit indicators and calculating anticipated operational size and throughput rate before the actual database modification execution. This allows execution time to be estimated in advance using the formula: anticipated total execution time = anticipated operational size / anticipated operational throughput rate, resolving the contradiction by providing accurate predictions without requiring complex real-time monitoring during execution.
Solution Approach 2:
The patent introduces operational unit indicators as intermediary elements that bridge the gap between database modification statements and execution time prediction. These indicators serve as measurable proxies that enable the estimation system to calculate execution properties without directly instrumenting the database engine, thus maintaining simplicity while achieving measurement precision.
2Loss of information
If operational unit indicators are generated to enable execution time estimation, then measurement precision improves, but the complexity of tracking and calculating operational metrics increases
Solution Approach 1:
The patent segments the database modification execution into discrete operational unit indicators that can be individually identified and counted. By breaking down the execution process into measurable units (such as number of rows affected, pages modified, or operations performed), the system achieves complete execution property information without requiring complex holistic tracking mechanisms.
Data Source
AI summary
A computer-implemented method includes identifying one or more database modification statements and identifying one or more operational unit indicators. The one or more operation unit indicators are caused to be generated by the one or more database modification statements. An anticipated operational size is determined. The anticipated operational size is an estimated total number of the one or more operational unit indicators. An anticipated operational throughput rate is determined. The anticipated operational throughput rate is a rate at which the operational unit indicators are expected to be generated. An anticipated total execution time of the one or more database modification statements is determined based on the anticipated operational size and the anticipated operational throughput rate. A corresponding computer program product and computer system are also disclosed.