Nested Multiproviders Merging for Database Query Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Complex calculations involving numerous queries between an application server and a database server consume significant resources due to unnecessary intermediate results and redundant aggregations, leading to inefficient query processing.
Innovation Solution
A database system that instantiates and optimizes calculation scenarios by merging nested multiproviders, combining attributes, and omitting unnecessary paths and attributes, thereby reducing redundant aggregations and improving query efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If complex calculations involve numerous queries between application server and database server, then calculation results can be obtained, but significant resources are consumed due to unnecessary intermediate results and redundant aggregations
Solution Approach 1:
The patent merges nested multiproviders by combining their attributes and part providers into a single unified multiprovider structure. This eliminates redundant intermediate results and aggregations by consolidating multiple data provider layers that previously operated separately, thereby reducing resource consumption while maintaining calculation accuracy
Solution Approach 2:
The optimization process extracts and removes unnecessary intermediate results and redundant aggregation operations from the calculation scenario. By identifying and eliminating these extraneous computational steps, the system reduces resource consumption without affecting the final calculation outcome
2Productivity
If nested multiproviders are merged, then redundant aggregations are reduced and query efficiency improves, but the complexity of the optimization process increases
Solution Approach 1:
The system performs preliminary analysis of the calculation scenario to identify mergeable multiproviders before executing the merging operation. This preliminary assessment includes checking compatibility of attributes and part providers, which simplifies the main merging process by pre-processing the optimization logic and avoiding complex runtime decisions
3Reliability
If all paths and attributes in calculation scenario are processed, then complete calculation results are obtained, but unnecessary paths and attributes increase query overhead
Solution Approach 1:
The instantiation process extracts only the necessary paths and attributes required to respond to the specific query from the complete calculation scenario. By identifying and removing unnecessary computational paths and attributes, the system reduces query overhead while ensuring all required data for the calculation is retained
Data Source
AI summary
A query is received by a database server from a remote application server that is associated with a calculation scenario that defines a data flow model including one or more calculation nodes including stacked multiproviders. Subsequently, the database server instantiates the calculation scenario and afterwards optimizes the calculation scenario. As part of the optimization, the calculation scenario is optimized by merging the two multiproviders. Thereafter, the operations defined by the calculation nodes of the optimized calculation scenario can be executed to result in a responsive data set. Next, the data set is provided to the application server by the database server.