Projection View Remapping for Zero-Downtime ERP Table Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The deployment of configuration data in enterprise resource planning (ERP) systems is cumbersome and often requires several hours or even up to a day, during which the system cannot be used due to the complex activation process conflicting with existing processes and the need to synchronize thousands of tables.
Innovation Solution
A method involving the creation of a second set of database tables (mod tables) during a modification operation, with a projection view remapping to allow simultaneous access to both sets of tables, enabling seamless transitions and reducing downtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If configuration data deployment is performed using traditional methods with complex activation process, then the system ensures data consistency and reliability, but the deployment time increases to several hours or up to a day and the system becomes unavailable during this period
Solution Approach 1:
The patent segments the configuration data into multiple independent tables organized in a tree structure. Each table can be deployed and activated independently rather than requiring simultaneous deployment of all 25,000 tables. This segmentation allows the deployment process to be divided into smaller, parallelizable units that can be processed concurrently, reducing overall deployment time while maintaining data consistency through the hierarchical structure.
Solution Approach 2:
The patent creates a copy of the configuration data in a target environment and applies transformations to the copied data during deployment. Instead of modifying the source data directly, the system copies configuration tables to the target system and applies pending changes to these copies, allowing the source system to remain operational while deployment occurs on the target copy.
2Reliability
If all database tables are synchronized and attached during deployment, then the system ensures complete data consistency, but the system cannot be used during this time causing operational downtime
Solution Approach 1:
The patent implements dynamic table attachment and detachment mechanisms that allow the system to selectively attach only the specific configuration tables that need to be deployed, rather than attaching all 25,000 tables simultaneously. The system can dynamically manage table states, attaching individual tables as needed for deployment operations and detaching them when complete, allowing other system operations to continue in parallel with selective table synchronization.
Solution Approach 2:
The patent performs preliminary actions by pre-compiling and staging configuration changes before actual deployment. The system prepares transformation rules and pending changes in advance, so that when deployment occurs, the changes can be applied quickly to the target tables without requiring prolonged system unavailability. The preliminary preparation allows the actual deployment to be completed in minutes rather than hours.
3Reliability
If a complex activation process is used to deploy configuration data across thousands of tables, then the system ensures thorough deployment, but the deployment process becomes cumbersome and conflicts with existing ERP and CRM processes
Solution Approach 1:
The patent introduces an intermediary transformation layer that mediates between the source configuration data and the target system. Instead of directly deploying raw configuration data through a complex activation process, the system uses transformation rules and a projection view as intermediaries to convert and stage the data. This intermediary layer simplifies the deployment process by handling the complexity of coordinating thousands of tables behind a unified transformation interface, making the process more manageable and less prone to conflicts with existing ERP and CRM processes.
4Reliability
If the system attaches and synchronizes thousands of tables during deployment, then the system ensures complete configuration deployment, but the deployment duration extends to several hours or a day
Solution Approach 1:
The patent implements periodic action by deploying configuration data in multiple phases or batches rather than attempting to deploy all tables simultaneously. The system can process tables in periodic batches, allowing intermediate commits and maintaining system operability between batches. This phased approach divides the lengthy deployment process into manageable periods, reducing the impact on system availability and allowing shorter, more frequent deployment cycles that collectively achieve complete configuration deployment.
Data Source
AI summary
One or more applications access a first set of database tables via a first projection view mapping from a first name to a second name. At a given point in time, the one or more applications may detect an indication of a modification operation targeting the first set of database tables. In response to detecting the indication of the modification operation, the one or more applications may create a second set of database tables for storing results of the modification operation. In response to detecting a completion of the modification operation, the first projection view may be remapped from the first name to a third name, where the third name is associated with the second set of database tables. Then, the one or more applications may access the second set of database tables via the first projection view mapping from the first name to the third name.