Database system and methods

• US 7,249,118 B2
• Filed: 05/17/2002
• Issued: 07/24/2007
• Est. Priority Date: 05/17/2002
• Status: Active Grant

• Current Assignee: Sybase Incorporated (SAP SE)
• Original Assignee: Aleri (SAP SE)
• Inventors: Kornilovski, Alexandre, Seroff, Vladimir, Sandler, Zigmund, Kolodzieski, Scott J.
• Primary Examiner(s): Gaffin; Jeffrey
• Assistant Examiner(s): Mahmoudi; Hassan
• Application Number:
  US10/150,763
• Publication Number:
  US 20030217033A1
• Time in Patent Office: 1,894 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2264 Multidimensional index structures
• CPC Class Codes: G06F 16/2272 Management thereof
• CPC Class Codes: Y10S 707/99931 Database or file accessing

Abstract

In general, in one aspect, the invention relates to a method for transaction processing. The method includes specifying metadata and storing the metadata. An index is created in response to the stored metadata. The method also includes receiving a transaction, generating an index log of changes to the index in response to the received transaction, and modifying the first index in response to the generated index log.

Claims

1. A method for checkpointing in a transaction processing system in communication with a plurality of systems external to the transaction processing system, the method comprising:

specifying a plurality of systems external to the transaction processing system that are each in communication with the transaction processing system and are each subscribers to a common data table, wherein one or more of the subscribers comprises an application server;

communicating to each of the specified subscribers a copy of the data table for storing by each of the subscribers as a local copy of the data table; and

communicating log entries to the each of the specified subscribers, the log entries comprising changes to the data table resulting from transactions affecting the data table, and wherein the log entries comprise change data provided to a checkpointing subsystem.

2. The method of claim 1 wherein one or more of the subscribers comprises an OLAP server.

3. The method of claim 2, further comprising, receiving, by one OLAP server, the copy of the data table, and storing the copy of the data table as a local copy of the data table.

4. The method of claim 3, further comprising, receiving by the one OLAP server the log entries.

5. The method of claim 4, further comprising applying, by the one OLAP server, the log entries to the local copy of the data table.

6. The method of claim 2, wherein one OLAP server performs additional operations on the log entries before applying them to its copy of the data table.

7. The method of claim 1, further comprising the steps of:

determining whether a number of log entries is above a predetermined threshold;

applying the log entries to the data table, and communicating an updated data table to the subscribers if the number of log entries is above a predetermined threshold; and

communicating to the specified subscribers additional log entries, the additional log entries comprising further changes to the data table resulting from transactions, if the number of log entries is not above the predetermined threshold.

8. A method for checkpointing in a transaction processing system in communication with a system external to the transaction processing system, the method comprising:

specifying a system external to the transaction processing system that is in communication with the transaction processing system to be a subscriber to a data table;

communicating a copy of the data table to the specified subscriber;

communicating log entries to the specified subscriber, the log entries comprising changes to the data table resulting from transactions affecting the data table;

determining whether a number of log entries is above a predetermined threshold;

applying the log entries to the data table, and communicating an updated data table to the subscriber if the number of log entries is above a predetermined threshold; and

communicating to the specified subscriber additional log entries, the additional log entries comprising further changes to the data table resulting from transactions, if the number of log entries is not above the predetermined threshold.

9. The method of claim 8 wherein the subscriber comprises an OLAP server.

10. The method of claim 9, further comprising, receiving, by the OLAP server, the copy of the data table, and storing the copy of the data table as a local copy of the data table.

11. The method of claim 10, further comprising, receiving by the OLAP server the log entries.

12. The method of claim 11, further comprising applying, by the OLAP server, the log entries to the local copy of the data table.

13. The method of claim 9, wherein the OLAP server analyzes the log entries.

14. The method of claim 9, wherein the OLAP server performs additional operations on the log entries before applying them to its copy of the data table.

15. The method of claim 8 wherein the log entries comprise change data provided to a checkpointing subsystem.

16. The method of claim 8, further comprising, prior to the step of communicating log entries, computing the effects of a batch of transactions on the data table.

17. The method of claim 16, further comprising storing the effects of the batch of transactions on the data table as log entries.

18. The method of claim 8, wherein:

the specifying step further comprises specifying a plurality of systems external to the transaction processing system that are each in communication with the transaction processing system and are each subscribers to the data table;

communicating the data table comprises communicating to each of the specified subscribers a copy of the data table; and

communicating log entries comprises communicating log entries to the each of the specified subscribers.