Database Trigger Firing Criteria Using Operation Statement Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database systems incur unnecessary computational overhead due to frequent execution of database triggers, even when the trigger conditions are not met, leading to inefficient resource utilization.
Innovation Solution
Implement database triggers with firing criteria that define execution based on non-updated fields, using an AND combination of columns to reduce unnecessary trigger firings by analyzing the database operation statement before execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If database triggers are executed frequently to ensure data integrity, then reliability is improved, but computational overhead increases and resource utilization becomes inefficient
Solution Approach 1:
The patent analyzes the database operation statement before trigger execution to determine whether the trigger firing criteria are met. This preliminary analysis prevents unnecessary trigger executions by evaluating conditions such as whether specific columns are updated, thereby reducing computational overhead while maintaining data integrity when triggers are actually needed
Solution Approach 2:
Instead of executing triggers for all database operations, the patent implements selective trigger firing based on partial analysis of operation statements. The system performs only the necessary analysis to determine trigger eligibility, avoiding excessive computation while ensuring triggers fire when required for data integrity
2Reliability
If database triggers are executed for every operation to ensure data integrity, then reliability is improved, but productivity decreases due to unnecessary executions
Solution Approach 1:
The system performs preliminary analysis of database operation statements to determine trigger firing criteria before actual trigger execution. This early evaluation identifies operations that should not trigger trigger execution, thereby improving database operation efficiency while maintaining data integrity for operations that do require triggers
Solution Approach 2:
The patent extracts and analyzes specific components of database operation statements (such as column update information) to determine trigger eligibility. By taking out only the necessary information for trigger decision-making, the system avoids unnecessary trigger executions and improves overall database productivity
3Productivity
If trigger firing criteria are simplified for faster evaluation, then productivity is improved, but measurement precision of trigger conditions decreases
Solution Approach 1:
The patent segments trigger firing criteria into distinct, analyzable components within database operation statements. By dividing the evaluation into separate checks (such as column-level updates), the system achieves both efficient evaluation speed and accurate determination of trigger conditions
Data Source
AI summary
Database trigger firing techniques for reducing unnecessary trigger firings are disclosed. In one embodiment a computer system stores trigger information relating to initiating execution of at least one trigger instruction for a database in connection with a database operation statement. The trigger information includes a first set of one or more database field identifiers for a first set of one or more fields in the database and a second set of one or more database field identifiers for a second set of one or more fields in the database. The computer system receives a database operation statement and makes determinations that at least one field within the first set of fields and at least one field within the second set of fields is specified by the database operation statement. Based at least in part on the determinations, the computer system initiates execution of the at least one trigger instruction.