Compatibility Server for Database Rehosting

• US 20100094838A1
• Filed: 10/27/2008
• Published: 04/15/2010
• Est. Priority Date: 10/10/2008
• Status: Abandoned Application

• Current Assignee: Ants Software, Inc.
• Original Assignee: Ants Software, Inc.
• Inventors: Kozak, Joseph
• Application Number:
  US12/259,210
• Publication Number:
  US 20100094838A1
• Time in Patent Office: Days
• US Class Current: 707/705
• CPC Class Codes: G06F 16/2443 Stored procedures

Abstract

A system and method describing a compatibility server for rehosting database applications written for a specific vendor'"'"'s database on the database of a second vendor, without the need of rewriting the application to take into account differences in the application programming interfaces between the first vendor'"'"'s database and the second vendor'"'"'s database. Requests for access to the database are translated from one format to another at execution time. The server is also capable of translating error messages, data types and data formatting from the format used by the second database to that expected when making requests to the first database. Stored procedures defined in the first database are migrated to the second database as text blocks, and are translated at execution time into a high level programming language, compiled and executed against the second database. All information necessary for the mapping of schema, data, data types, error and status messages and data formatting, as well as information necessary to execute stored procedures, is stored in a plurality of metadata tables in the second database, which are created during a migration phase prior to executing the application.

Claims

1. A system for allowing an application written for a first database from a first vendor to be used with a second database from a second vendor comprising a compatibility server for emulating said second database when requests are received from an application written for said first database.

2. The system of claim 1 comprising:

a. a request translator, for translating requests in the dialect of said first database to the dialect of said second database; and

b. a request executor, for executing said translated requests against said second database.

3. The system of claim 2 further comprising a message handler;

for translating error and status messages received from said second database to those used by said first database.

4. The system of claim 1 further comprising a store of metadata describing mappings of objects and structure between said first database and said second database.

5. The system of claim 4 wherein said store of metadata is resident in one or more tables in said second database.

6. The system of claim 4 wherein said store of metadata is resident external to said second database

7. The system of claim 4 further comprising a metadata handler for reading and interpreting said metadata.

8. The system of claim 4 wherein said second database contains procedures copied from said first database.

9. The system of claim 8 wherein said procedures are stored in said second database as one of a group consisting of a procedure in the dialect of said second database, a procedure in an interim form and a text block containing the procedure in the dialect of said first database.

10. The system of claim 8 further comprising a stored procedure handler for interpreting, emulating or translating said procedures for execution against said second database.

11. The system of claim 8 wherein procedures stored as text blocks in said second database are translated into a high level programming language, compiled, and executed against said second database.

12. The system of claim 11 wherein said translation of said procedure occurs at execution time.

13. The system of claim 4 further comprising a component for formatting the results of queries from said second database to a format expected from said first database.

14. The system of claim 4 further comprising a data type handler for translating from data types used by said first database to data types used by said second database.

15. The system of claim 2 further comprising a component for interfacing with other instances of said system for accessing remotely located databases.

16. The system of claim 4 further comprising a migration component for analyzing differences between said first database and said second database, for creating said metadata store, and for reading procedures stored in said first database and storing said procedures in said second database.

17. The system of claim 16 wherein said migration component copies schema and data from said first database to said second database.

18. The system of claim 4 further comprising a privilege and authentication checker, for verifying the rights of users with respect to requests for access to said first database.

19. The system of claim 18 wherein information regarding the authentication and privileges of said users is stored in said metadata store.

20. A method for allowing an application written for a first database from a first vendor to be used with a second database from a second vendor comprising the step of providing an interface to said second database which caused said second database to emulate said first database

21. The method of claim 20 further comprising the steps of:

a. receiving requests for data queries, data storage and database manipulation from an application running on a computer, said requests being in a format required by said first database;

b. translating said received requests into a format required by said second database;

c. executing said translated request against said second database;

d. formatting results received from said first database in response to said request to a form expected from a request to said first database.

22. The method of claim 20 wherein said formatting results step further comprises the steps of:

a. mapping from data types defined by said second database to data types defined by said first database;

b. formatting received data to a form expected from a request to said first database;

c. mapping error and status messages received from said second database to a form expected from said first database.

23. The method of claim 22 further comprising the step of:

a. reading metadata from metadata stores, said metadata containing information about the mappings of data types from said second database to said first database, information about formatting data received from said second database to a form expected from said first database and information regarding the mapping of said error and status messages from said second database in a form expected from said first database; and

b. using said metadata to complete said formatting step.

24. The method of claim 23 wherein said metadata contains information necessary for the execution of stored procedures, further comprising the step of reading said metadata regarding said stored procedures when a request for execution of a stored procedure is received.

25. The method of claim 24 wherein said metadata regarding stored procedures includes information regarding whether said stored procedures are stored in the format of said second database or are stored in an interim form.

26. The method of claim 25 further comprising the steps of:

a. determining if said stored procedure is stored as a text block in the source language of said first database, and if so, continuing;

b. reading said stored procedure as a text block;

c. translating said stored procedure into a known computer language, including calls to an API for said second database;

d. compiling said translated stored procedure into an executable; and

e. executing said stored procedure against said second database.

27. The method of claim 21 further comprising the step of checking the syntax of said received requests to ensure that they comply with the request format required by said first database.

28. The method of claim 23 further comprising the step of checking the authentication and privileges of users making said requests.

29. The method of claim 28 further comprising the step of retrieving information regarding the privileges and authentication of said users from said metadata stores.

30. A compatibility server for allowing an application running on a client written for a first database from a first vendor to be used with a second database from a second vendor comprising:

a. a communications component, for handling communications between said application running on said client and said compatibility server;

b. a syntax checker, for verifying that requests for database access received from said application are in the dialect of said first database;

c. a request translator, for translating requests in the dialect of said first database to the dialect of said second database;

d. a request executor, for executing said translated requests against said second database;

e. a message handler;

for translating error and status messages received from said second database to those used by said first database;

f. a result set handler, for formatting the results of queries from said second database to a format expected from said first database;

g. a data type handler for translating from data types used by said second database to data types used by said first database;

h. a privilege and authentication checker, for verifying the rights of users with respect to said requests; and

i. a metadata handler for reading and interpreting metadata, said metadata describing mappings between said first database and said second database, said mappings including information regarding objects selected from a group comprising users, schema, data, data types, triggers, stored procedures, error and status messages and result set formats.

31. The compatibility server of claim 30 wherein said second database contains procedures stored as text blocks copied from said first database, further comprising a stored procedure handler for translating said procedures stored as text blocks into a programming language, compiling said translated procedure and executing said compiled procedure against said second database.

32. The compatibility server of claim 30 further comprising a component for interfacing with other instances of said compatibility server for accessing remotely located databases.