Systems and methods for database configuration migration

• US 7,024,412 B1
• Filed: 11/07/2001
• Issued: 04/04/2006
• Est. Priority Date: 11/07/2001
• Status: Expired due to Term

• Current Assignee: Rakuten Group, Inc.
• Original Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Inventors: Harris, Keith R., Webb, Sandra S., Devulapalli, Ravi R.
• Primary Examiner(s): Rones, Charles
• Assistant Examiner(s): AL HASHEMI, SANA A
• Application Number:
  US09/986,148
• Time in Patent Office: 1,609 Days
• Field of Search: 707/100, 707/102, 707/104.1, 707/10, 709/213
• US Class Current: 707/615
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

Embodiments of the present invention relate to systems and methods for database configuration migration. In an embodiment, the method includes receiving an instruction to hold constant a configuration of a first database. A change is implemented in a configuration of a second database. A configuration change transaction record based at least in part on the change in the configuration of the second database is stored. The configuration change transaction record is sent. A change in the configuration of the first database is implemented based at least in part on the configuration change transaction record.

Claims

1. A method for database configuration migration, the method comprising:

providing a first database having a configuration that specifies a number of data fields, a length of each data field, and a type of data for each data field;

copying the configuration of the first database to a second database;

receiving an instruction to hold constant the configuration of the first database;

implementing a change in the configuration of the second database;

storing a configuration change transaction record based at least in part on the change in the configuration of the second database;

sending the configuration change transaction record; and

implementing a change in the configuration of the first database based at least in part on the configuration change transaction record such that the changed configuration of the first database is the same as the changed configuration of the second database.

2. The method of claim 1, wherein the first database includes first configuration data and a first plurality of data records.

3. The method of claim 2, further comprising holding constant the first configuration data based at least in part on receiving the instruction to hold constant the configuration of the first database.

4. The method of claim 3, further comprising modifying one or more of the first plurality of data records.

5. The method of claim 3, further comprising adding one or more data records to the first plurality of data records.

6. The method of claim 3, further comprising deleting one or more data records of the first plurality of data records.

7. The method of claim 1, wherein the first database includes first configuration data, a first plurality of data records, and a first audit log.

8. The method of claim 1, wherein the second database includes second configuration data and a second plurality of data records.

9. The method of claim 8, wherein implementing the change in the configuration of the second database includes modifying the second configuration data.

10. The method of claim 8, wherein the second database includes a second audit log.

11. The method of claim 10, wherein implementing the change in the configuration of the second database includes modifying the second audit log based at least in part on implementing the change in the configuration of the second database.

12. A method for database configuration migration, the method comprising:

operating a first database and a second database, the first database including a first configuration that specifies a number of data fields, a length of each data field, and a type of data for each data field, the second database including a second configuration that is a copy of the first configuration;

implementing a change the configuration of the second database;

storing a configuration change transaction record based at least in part on the change in the configuration of the second database;

sending the configuration change transaction record; and

changing the configuration of the first database based at least in part on the configuration change transaction record that is based on the changed configuration of the second database such that the changed first configuration is the same as the changed second configuration.

13. The method of claim 12, wherein storing the configuration change transaction record includes storing the configuration change transaction record on a server.

14. The method of claim 12, further comprising holding constant the configuration of the first database prior to changing the configuration of the second database.

15. The method of claim 12, wherein the configuration change transaction record is stored in a transportable file format.

16. The method of claim 15, wherein the configuration change transaction record is sent from a host server to a remote server, the host server coupled to the second database, the remote server coupled to the first database.

17. The method of claim 15, wherein the configuration change transaction record is sent from a host server to a remote server, the host server coupled to the first database, the remote server coupled to the second database.

18. A system for database configuration migration, the system comprising:

means for operating a first database and a second database, the first database including a first configuration that specifies a first configuration having a number of data fields, a length of each data field, and a type of data for each data field, the second database including a second configuration that is a copy of the first configuration;

means for implementing a change in the configuration of the second database; and

means for storing a configuration change transaction record based at least in part on the change in the configuration of the second database;

means for sending the configuration change transaction record; and

means for changing the configuration of the first database based at least in part on the configuration change transaction record that is based on the changed configuration of the second database such that the changed first configuration is the same as the changed second configuration.

19. The system of claim 18, wherein the configuration change transaction record is stored in a transportable file format.

20. The system of claim 18, further comprising means for holding constant the configuration of the first database prior to changing the configuration of the second database.

21. A method for database configuration migration, the method comprising:

a step for operating a first database and a second database, the first database including a first configuration that specifies a first configuration having a number of data fields, a length of each data field, and a type of data for each data field, the second database including a second configuration that is a copy of the first configuration;

a step for implementing a change in the configuration of the second database;

a step for storing a configuration change transaction record based at least in part on the change in the configuration of the second database;

a step for sending the configuration change transaction record; and

a step for changing the configuration of the first database based at least in part on the configuration change transaction record that is based on the changed configuration of the second database such that the changed first configuration is the same as the changed second configuration.

22. The method of claim 21, wherein the configuration change transaction record is stored in a transportable file format.

23. The method of claim 21, further comprising a step for holding constant the configuration of the first database prior to changing the configuration of the second database.

24. A computer-readable medium storing a plurality of instructions to be executed by a processor for database configuration migration, the plurality of instructions comprising instructions to:

communicate with a first database and a second database, the first database including a first configuration that specifies a first configuration having a number of data fields, a length of each data field, and a type of data for each data field, the second database including a second configuration that is a copy of the first configuration;

implement a change in the configuration of the second database;

store a configuration change transaction record based at least in part on the change in the configuration of the second database;

send the configuration change transaction record; and

change the configuration of the first database based at least in part on the configuration change transaction record that is based on the changed configuration of the second database such that the changed first configuration is the same as the changed second configuration.

25. The computer-readable medium of claim 24, wherein the configuration change transaction record is stored in a transportable file format.

26. The computer-readable medium of claim 24, further comprising instructions to hold constant the configuration of the first database prior to changing the configuration of the second database.