No Rollback Threshold Audit Trail Transaction Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As databases grow in size and complexity, traditional audit trails face challenges in managing transaction logs, leading to potential space exhaustion and prolonged rollback processes, which can cause extended outages and increased costs due to the need for additional storage and recovery times.
Innovation Solution
Implementing a no rollback threshold in audit trails, where transactions exceeding a specified capacity are converted to a no rollback state, allowing them to be abandoned instead of rolled back, thereby preventing prolonged lock-downs and reducing the need for off-platform storage and recovery processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional audit trails are used to log all transactions for recovery purposes, then transaction reliability is improved, but storage space is exhausted and rollback processes are prolonged
Solution Approach 1:
The patent changes the state parameter of transactions by introducing a 'no rollback' flag that alters how transactions are handled. When this parameter is set, transactions are abandoned rather than rolled back, fundamentally changing the recovery mechanism and reducing storage requirements while maintaining reliability for critical transactions.
Solution Approach 2:
The patent segments transactions into two categories: those that require rollback capability (traditional audit trail) and those that use the no rollback mechanism. This segmentation allows the system to optimize storage by applying different handling strategies to different transaction types, reducing overall audit trail space consumption.
2Stability of the object's composition
If traditional rollback processes are used for failed transactions, then data consistency is maintained, but system outage time is extended
Solution Approach 1:
The patent applies preliminary action by pre-setting the no rollback flag on transactions before they fail. This allows the system to immediately abandon failed no rollback transactions without initiating prolonged rollback processes, significantly reducing system outage time while maintaining data consistency through selective transaction abandonment.
3Productivity
If audit trail capacity is increased to accommodate large transactions, then transaction processing capability is improved, but storage costs increase
Solution Approach 1:
The patent extracts the rollback capability from transactions that don't need it by applying the no rollback flag. This extraction allows the system to process large transactions without proportionally increasing audit trail capacity, as these transactions don't require full rollback support, thereby reducing storage capacity requirements while maintaining processing capability.
Data Source
AI summary
Examples of a no rollback threshold for an audit trail are disclosed. In one example implementation according to aspects of the present disclosure, a method may include processing, by a computing system, a database transaction, and determining, by the computing system, whether a transaction span of the transaction exceeds a no rollback threshold for an audit trail. The method may include, in response to determining that the transaction span exceeds the no rollback threshold, converting, by the computing system, the transaction into a no rollback transaction. Additionally, the method may include, in response to determining that the transaction span exceeds the no rollback threshold, abandoning, by the computing system, the transaction if an error is encountered during the processing the transaction.