System and method of combined database system

• US 9,223,848 B2
• Filed: 10/29/2012
• Issued: 12/29/2015
• Est. Priority Date: 10/31/2011
• Status: Active Grant

• Current Assignee: Cognyte Technologies Israel Ltd. (Cognyte Software Ltd.)
• Original Assignee: Verint Systems Limited (Verint Systems Incorporated)
• Inventors: Wilf, Yuval
• Primary Examiner(s): Mofiz, Apu
• Assistant Examiner(s): Bibbee, Jared
• Application Number:
  US13/663,384
• Publication Number:
  US 20130110764A1
• Time in Patent Office: 1,156 Days
• Field of Search: 707/600
• US Class Current: 1/1
• CPC Class Codes: G06F 16/283 Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP

Abstract

A system, including both an OLTP database and a warehouse database, that is configured to manage the coordination between the OLTP database and the warehouse database. An aspect relates to a combined OLTP and warehouse database which manages duplicate copies, in both the OLTP database and the warehouse database, of data expected to have a relatively high update and query rate. Data which has a low update and query rate is removed from the OLTP database, such that it remains only in the warehouse database. Updates of the duplicate copy data are performed in the OLTP. Periodically, for example every several minutes, data recently changed in the OLTP database is copied to the warehouse database. Queries are optionally primarily handled by the warehouse database, and are supplemented, when necessary, by data from the OLTP database.

Claims

1. A database system, comprising:

an online transaction processing (OLTP) database;

a warehouse database comprising a short term storage area and a long term record storage area; and

an application server comprising a processor coupled to a memory, wherein the application server is configured to manage coordination between the OLTP database and the warehouse database by at least;

periodically duplicating and storing to the short term area of the warehouse database, using an ETL (Extract, Transform, Load) process, all data that has recently been added or changed in the OLTP database, wherein the duplicating and storing is performed at a rate selected in such a way so that during the duplicating and storing at least a predetermined percentage of database queries can be handled by the warehouse database without use of the OLTP database, and

after a predetermined amount of time from when the data is duplicated and stored to the warehouse database, moving the duplicated data from the short term area of the warehouse database to the long term area of the warehouse database and removing from the OLTP database the recently added or changed data;

wherein the application server is configured such that the OLTP database does not store data which is not also stored in the warehouse database, except for data recently added or changed in the OLTP database which has not yet been duplicated and stored to the warehouse database.

5. The system of claim 1, wherein the application server is further configured to estimate whether received queries need real time information, and if so, forwarding the queries to the OLTP or to the short term area.

6. The system of claim 1, wherein the data stored in OLTP is removed only after the copied data has been successfully moved from the short term area of the warehouse database to the long term area of the warehouse database.

2. A method of managing a database, comprising:

providing an online transaction processing database (OLTP);

providing a warehouse database comprising a short term storage and a long term storage area;

providing an application server that is configured to manage coordination between the OLTP database and the warehouse database by at least;

periodically duplicating and storing to the short term area of the warehouse database, using an ETL (Extract, Transform, Load) process, all data that has been recently added or changed in OLTP database, wherein the duplicating and storing is performed at rate selected in such a way so that during the duplicating and storing, at least a predetermined percentage of database queries can be handled by the warehouse database without use of the OLTP database, and

after a predetermined amount of time from when the data is duplicated and stored, moving the duplicated data from the short term area of the warehouse database to the long term area of the warehouse database and removing the recently changed or added data from the OLTP database;

wherein the application server is configured such that the OLTP database does not store data which is not also stored in the warehouse database, except for data recently added or changed in the OLTP database which has not yet been duplicated and stored to the warehouse database.

3. The method of claim 2, comprising estimating whether received queries need real time information, and if so, forwarding the queries to the OLTP or to the short term area.

4. The method of claim 2, wherein the data stored in OLTP is removed only after the copied data has been successfully moved from the short term area of the warehouse database to the long term area of the warehouse database.