Standby Database Data Compartments for Read-Write Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current standby databases are limited to read-only access, preventing them from supporting read-write activity, which hinders their use for building pre-production databases, performing incremental application tests, receiving updates, and switching between production and pre-production data versions, thereby rendering off-the-shelf reporting tools ineffective.
Innovation Solution
Implementing a system that creates separate data compartments on a standby database with read-write capability while maintaining data consistency with the primary database, allowing for real-time updates and flexible data management, including the ability to clone instances quickly and maintain multiple compartments for reporting and testing purposes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If standby database is designed for read-only access to maintain data consistency with primary database, then data consistency is preserved, but read-write capability is lost
Solution Approach 1:
The standby database is segmented into multiple data compartments (first data compartment, second data compartment, third data compartment) with different access permissions. The first data compartment allows read-write operations for pre-production activities, the second data compartment maintains read-only access for disaster recovery, and the third data compartment supports reporting operations. This segmentation enables simultaneous read-write and read-only capabilities while maintaining data consistency through selective data propagation from the primary database.
2Adaptability or versatility
If standby database allows read-write activity, then versatility for pre-production and testing is improved, but data consistency with primary database deteriorates
Solution Approach 1:
Different data compartments are assigned different quality characteristics regarding data consistency. The first data compartment accepts local modifications for pre-production work, the second data compartment maintains strict consistency with the primary database through read-only access, and the third data compartment is selectively updated based on merge rules. This local quality differentiation allows read-write activity in specific compartments while preserving data consistency in others.
Solution Approach 2:
The system dynamically determines whether to apply changes from the primary database to each data compartment based on merge rules. The processor evaluates changes in real-time and selectively propagates them to the first, second, and third data compartments according to their specific requirements and current state, enabling flexible data consistency management that adapts to different operational contexts.
3Adaptability or versatility
If separate data compartments are created for different purposes, then versatility is improved, but device complexity increases
Solution Approach 1:
The standby database system is designed as a multi-functional platform that simultaneously supports disaster recovery (second data compartment), pre-production activities (first data compartment), and reporting operations (third data compartment). By consolidating multiple specialized databases into a single universal standby database with compartmentalized data storage, the system reduces overall complexity while maintaining versatile functionality across different operational requirements.
Data Source
AI summary
A method for creating a standby database with read/write access capability while also maintaining a data consistency with a primary database, is provided. The method includes syncing the primary database with a physical standby mirror existing on the standby database, creating a first data compartment and a second data compartment on the standby database, separate from the physical standby mirror, applying a change made to the first data object on the primary database to the corresponding first data object on the physical standby mirror; and determining whether the change should be applied to the corresponding first data object stored on the first data compartment in accordance with data merge rules associated with the first data compartment and the second data compartment.