Universe migration from one database to another

• US 9,176,997 B2
• Filed: 06/28/2013
• Issued: 11/03/2015
• Est. Priority Date: 06/28/2013
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Balasubramanian, Makesh, Vundavalli, Venkatram
• Primary Examiner(s): WILLOUGHBY, ALICIA M
• Application Number:
  US13/929,796
• Publication Number:
  US 20150006490A1
• Time in Patent Office: 858 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity

Abstract

A semantic layer (universe), which is created on a source database (DB), is migrated to a target DB. The migration includes pre-migration steps, actual migration and post-migration steps. The pre-migration steps prepare the target DB for the actual migration by configuring the target DB and determining the differences between the source DB and the target DB. During the actual migration, data, tables and views are migrated to the target DB conforming to the target database structure, functions and configuration. A new universe is created on the target database and all consumers of the source universe such as created reports are changed to refer to the new universe.

Claims

1. A computer implemented method for universe migration from a source database (DB) to a target DB, comprising:

selecting a source universe for migration, the source universe using the source DB through a source connection and selecting a target connection to the target DB;

based on the source connection and the target connection, loading configuration data comprising mapping of one or more DB functions of the source DB and the target DB;

examining the source universe, by;

determining the list of used tables in the source DB;

determining joins and contexts for the determined list of used tables;

determining a list of objects; and

determining security applied on the source universe;

generating a script to create one or more corresponding tables in the target DB, wherein the created one or more corresponding tables are from a list of used tables in the source DB unavailable in the target DB compared to the source DB;

checking integrity of available and created tables in the target DB;

creating a new data foundation in the target DB, by;

adding tables and views to the target DB from the list of used tables in the source DB;

adding alias tables and derived tables to the target DB from the list of used tables in the source DB based on dependency logic;

creating joins and replicating contexts from the source universe; and

replicating objects by replacing queries to the source DB with queries to the target DB;

creating a new universe based on the new data foundation;

persisting the new universe and checking integrity of the new universe; and

determining reports created on the source universe and adapting the reports to point to the new universe.

2. The method of claim 1, wherein the list of used tables comprises tables, views, alias tables and derived tables.

3. The method of claim 1, wherein determining the list of objects further comprises identifying used DB functions.

4. The method of claim 1, wherein the objects are one or more selected from the group consisting of dimensions, details, measures, and filters.

5. The method of claim 1, determining the security applied on the source universe further comprises:

examining one or more security rules; and

determining one or more queries containing DB functions.

6. A computer system for universe migration from a source database (DB) to a target DB, comprising:

a processor; and

a memory in communication with the processor, the memory storing instructions related to;

a source universe using the source DB through a source connection;

a new universe using the target DB through a target connection;

a loading engine that loads, based on the source connection and the target connection, configuration data comprising mapping of one or more DB functions of the source DB and the target DB;

a script generator engine that generates a script to create one or more corresponding tables in the target DB, wherein the created one or more corresponding tables are from a list of used tables in the source DB unavailable in the target DB;

a data foundation generator that creates a new data foundation in the target DB by;

adding tables and views to the target DB from the list of used tables in the source DB;

adding alias tables and derived tables to the target DB from the list of used tables in the source DB based on dependency logic;

creating joins and replicating contexts from the source universe; and

replicating objects by replacing queries to the source DB with queries to the target DB;

a universe generator that creates the new universe based on the new data foundation; and

a migration engine that;

examines the source universe by;

determining the list of used objects in the source DB;

determining joins and contexts for the determined list of used tables;

determining a list of objects; and

determining security applied on the source universe;

checks integrity of available and created tables in the target DB;

persists the new universe and check integrity of the new universe; and

determines reports created on the source universe and adapt the reports to point to the new universe.

7. The system of claim 6, wherein the list of used tables comprises tables, views, alias tables and derived tables.

8. The system of claim 6, wherein the migration engine is further operable to identify used DB functions.

9. The system of claim 6, wherein the objects are one or more selected from the group consisting of dimensions, details, measures, and filters.

10. The system of claim 6, wherein the migration engine is further operable to:

examine one or more security rules; and

determine one or more queries containing DB functions.

11. An article of manufacture including a non-transitory computer readable storage medium to tangibly store instructions, which when executed by a computer, cause the computer to:

select a source universe for migration, the source universe using a source DB through a source connection and to select a target connection to a target DB;

based on the source connection and the target connection, load configuration data through mapping of one or more DB functions of the source DB and the target DB;

examine the source universe by;

determining the list of used tables in the source DB;

determining joins and contexts for the determined list of used tables;

determining a list of objects; and

determining security applied on the source universe;

generate a script to create one or more corresponding tables in the target DB, wherein the created one or more corresponding tables are from a list of used tables in the source DB unavailable in the target DB compared to the source DB;

check integrity of available and created tables in the target DB;

create a new data foundation in the target DB by;

adding tables and views to the target DB from the list of used tables in the source DB;

adding alias tables and derived tables to the target DB from the list of used tables in the source DB based on dependency logic;

creating joins and replicating contexts from the source universe; and

replicating objects by replacing queries to the source DB with queries to the target DB;

create a new universe based on the new data foundation;

persist the new universe and check integrity of the new universe; and

determine reports created on the source universe and adapt the reports to point to the new universe.

12. The article of manufacture of claim 11, wherein the list of used tables comprises tables, views, alias tables and derived tables.

13. The article of manufacture of claim 11, wherein the instructions to determine the list of objects further comprise instructions, which when executed by a computer, cause the computer to identify used DB functions.

14. The article of manufacture of claim 11, wherein the objects are one or more selected from the group consisting of dimensions, details, measures, and filters.

15. The article of manufacture of claim 11, wherein the instructions to determine the security applied on the source universe further comprise instructions, which when executed by a computer, cause the computer to:

examine one or more security rules; and

determine one or more queries containing DB functions.