Patent application number | Description | Published |
20120089625 | INCREMENTAL CONVERSION OF DATABASE OBJECTS DURING UPGRADE OF AN ORIGINAL SYSTEM - A computer system can include a database comparator configured to identify a first database object from an original system for a complete modification based on a comparison of the first database object with a plurality of target upgrade database objects, and configured to identify a second database object from the original system for a partial modification based on a comparison of the second database object with the plurality of target upgrade database objects. A complete modification module can be configured to designate, in response to the identification of the first database object, the first database object for the complete modification based on an incremental conversion process. A partial modification module can be configured to designate the second database object for the partial modification based on the incremental conversion process when an instruction to implement the partial modification satisfies at least a portion of a modification condition. | 04-12-2012 |
20120137297 | MODIFYING SCHEDULED EXECUTION OF OBJECT MODIFICATION METHODS ASSOCIATED WITH DATABASE OBJECTS - An original schedule module configured to receive an original schedule configured to trigger execution of a first original batch of entries including a set of object modification methods and a corresponding set of database objects before triggering execution of a second original batch of entries including a set of object modification methods and a corresponding set of database objects. An analysis module can be configured to determine logic for execution of each entry from the first original batch of entries based on the original schedule. A schedule generator can be configured to define, based on the logic for execution and based on the original schedule, a modified schedule configured to trigger parallel execution of a first modified batch of entries including less than all of the first original batch of entries, and a second modified batch of entries including less than all of the second original batch of entries. | 05-31-2012 |
20120166393 | SHADOW SYSTEM MIRRORING OF AN ORIGINAL SYSTEM DURING UPTIME OF AN UPGRADE PROCESS - A computer system can include a program database module configured to define, at a shadow system, a shadow program database having a structure defining an upgrade to a structure of an original program database on an original system, and having data defining an upgrade to data of the original program database on the original system. The computer system can include a customization upgrade module configured to select the data of the shadow program database based on a data customization implemented in the original program database of the original system, and configured to define an upgraded program state of the shadow program database based on a combination of the structure of the shadow program database and the data of the shadow program database. | 06-28-2012 |
20120166493 | SHADOW SYSTEM START DURING UPGRADE OF AN ORIGINAL SYSTEM - In one general aspect, a computer system can include instructions stored on a non-transitory computer-readable storage medium. The computer system can include a program database module configured to define, at a shadow system, a shadow program database including data and a structure collectively defining an upgrade to an original program database on an original system. The computer system can include a basis module configured to define at the shadow system a shadow basis database related to start functionality of the shadow system. The computer system can also include a downtime execution module configured to trigger the shadow system to change from a downstate to an upstate based on a combination of data included in the shadow basis database and the data of the shadow program database. | 06-28-2012 |
20130159247 | CHANGE DATA CAPTURING DURING AN UPGRADE - In one general aspect, a computer system can include instructions stored on a non-transitory computer-readable storage medium. The computer system can include a logging table generator configured to generate a logging table corresponding with an original table targeted for an upgrade, and a control table generator configured to generate a control table configured to store a version identifier for changes logged in the logging table. The computer system can include a change recorder configured to receive an indicator of a change to a record of the original table during execution of at least a portion of the upgrade of the original table, and a key recorder configured to store in the logging table a primary key identifying the record of the original table and the version identifier stored in the control table. | 06-20-2013 |
20130238555 | ALIASES FOR ACCESSING SHARED TABLES DURING PROVISION OF CONTINUOUS ACCESS DURING APPLICATION UPGRADE - Continuous access to an application and associated data is provided during a modification (for example, an upgrade) of the application. Shared tables are used to perform parallel changes in databases associated with an original database schema, a temporary database schema, and an upgraded database schema. Aliases are used to access shared tables from some database schemas. The use of shared tables obviates a separate merging of data written by different tools and/or systems during an upgrade of the application. Related methods, apparatuses, systems, techniques and articles are also described. | 09-12-2013 |
20130238577 | PROVIDING CONTINUOUS DATABASE ACCESS DURING DATABASE MODIFICATION - The subject matter described herein relates to providing a continuous access to a database at times, including when the database is being modified or upgraded. Initially, access to an old version of a table is enabled and provided to a user. A copy of the old version is generated. Access is asynchronously redirected from the old version to the copy of the old version. A new version of the table is generated by modifying the structure of the first version of the table. The copy of the old version is accessible when the database is being modified or upgraded. When the structure is being modified, access is asynchronously redirected from the copy of the old version to the new version. | 09-12-2013 |
20130238868 | USING TEMPORARY SYSTEM TO PROVIDE CONTINUOUS ACCESS DURING APPLICATION UPGRADE - A temporary system is described to provide, during an upgrade of an application implemented using an original system, a continuous access to the application. A copy of a first data-set characterizing a first version of the application is generated on the temporary system when the upgrade becomes available. A selective access to the copy on the temporary system is enabled while preventing access to the first data-set on an original system. The first data-set on the original system is upgraded to form a second data-set characterizing a second version of the application, and a testing of the second data-set is performed. When a result of the testing indicates that the second data-set should be implemented, an access to the second data-set on the original system is enabled while preventing access to the copy on the temporary system. Related methods, apparatus, systems, techniques and articles are also described. | 09-12-2013 |
20130290259 | SHADOW SYSTEM MIRRORING OF AN ORIGINAL SYSTEM DURING UPTIME OF AN UPGRADE PROCESS - A computer system includes a shadow system including a shadow program database having a structure defining an upgrade to a structure of an original program database on an original system, and having data defining an upgrade to data of the original program database on the original system. The computer system includes a database replicator configured to perform at least one transfer of data from a portion of the original user database into the structure of the shadow user database during an uptime of the original system and configured to perform a final transfer of data from the portion of the original user database into the structure of the shadow user database during a downtime of the original system, and an upgrade transfer module configured to replace the portion of the original user database with the shadow user database after the final transfer of data has been performed. | 10-31-2013 |