Browse Prior Art Database

Apparatus and method to automatically analyze, verify and migrate database Disclosure Number: IPCOM000198748D
Publication Date: 2010-Aug-13
Document File: 6 page(s) / 88K

Publishing Venue

The Prior Art Database


This invention provides a series of ideas about how to improve the success of database migration by: - Identifying the differences between the source database and target database. - Identifying conflicts based on migration rules. - Calculating the resources and time required for database migration. - Generating an SQL file containing the differences between the two databases. - Serializing the database schema to be a binary file. This invention can speed up, automate, and simplify database migration.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 42% of the total text.

Page 1 of 6

Apparatus and method to automatically analyze , verify and migrate database

Disclosed is a framework for a set of innovative methods and tools to ease the pain of migration. By implementing the disclosed framework, users can typically plan migrations more effectively and perform migrations more efficiently than before using the disclosed framework.

Databases are used comprehensively in many products and when customers want to upgrade a


 roduct, database migration can be a time-consuming and frustrating experience. Customers are typically faced with topics that are not often easy to address including determining whether customization schema changes could cause the database migration to fail, determining whether there are obstacles to remove before attempting a database migration, determining how to migrate a database successfully, determining what resources are required and expected duration of the migration.

The disclosed framework, of Figure 1,

                        rovides a number of capabilities including analysis of differences between a source database and a target database; identification of conflicts caused by customization schema changes, using migration rules and configuration file, and adjusting a database accordingly; calculation of resources needed for database migration, using current database size and number of customization changes; estimation of the duration of the database migration using current database size and number of customization changes; identification of bottlenecks and avoidance scenarios, (for example, to reduce migration times, a database clean operation may be performed on a bottleneck area); automatic generation of delta Structured Query Language (SQL) between the source and target databases, using the analysis enabling use of the delta directly by the migration script; and serializing database schema information to a binary file for direct processing, eliminating a need to connect to the database.



Page 2 of 6

Figure 1

Embodiments of the disclosed framework typically provide significant reductions in the effort required for a product development team to maintain the schema changes for database migration. For example in a product release there are 4 major database management system (DBMS) types and there have been 50 database schema changes. Using traditional methods, the effort to maintain the schema changes is 100


erson days (PD). Using an embodiment of the disclosed

framework, the effort is reduced to 19


erson days,


roviding a savings of about 80


erson days

of effort. The table of Figure 2

provides additional details.

          Traditional way Using invention Precondition

1. 4 major DBMS type are supported by this product.
2. Handling schema delta effort for each DB type: 0.5 PD.
3. Average schema changes in the new release of product: 50

1. get schema delta for each DBMS type: 1PD*4 = 4 PD.
2. verify for each DBMS type:

3PD*4 = 12 PD.
3. check in code and finish code review process: 3 PD.

Effort 4*0.5*50 = 100 PD 4+12...