Method for enhancing the operation of a database

• US 20070260644A1
• Filed: 02/09/2006
• Published: 11/08/2007
• Est. Priority Date: 02/09/2006
• Status: Active Grant

• Current Assignee: Cinnober Financial Technology AB (Nasdaq, Inc.)
• Original Assignee: Cinnober Financial Technology AB (Nasdaq, Inc.)
• Inventors: Sellberg, Lars-Ivar, Ljungqvist, Mats
• Granted Patent: US 7,603,354 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database

Abstract

Methods, computer readable mediums, and computer program products for a computer system communicating with a plurality of clients, the system including at least a server, wherein the server receives incoming messages of the system, the server being connected to a SQL database for storing incoming messages, the method including: receiving updating instructions via incoming messages; storing the incoming messages in a file having a horizontal file structure; updating the database by performing updating operations according to the instructions of the messages; and performing a committing operation of all updating operations performed since the last committing operation at predetermined intervals in order to make all data modifications performed since the start of the last committing operation a permanent part of the database.

Claims

1. A method for a computer system communicating with a plurality of clients, said system including at least a server, wherein said server receives incoming messages of said system, said server being connected to a database for storing information according to instructions of said incoming messages, said method comprising the steps of:

receiving updating instructions via incoming messages;

storing said incoming messages in a file having a horizontal file structure;

updating said database by performing updating operations according to said instructions of said messages; and

performing a committing operation of all updating operations performed since said last committing operation at predetermined intervals in order to make all data modifications performed since the start of the last committing operation a permanent part of the database.

2. The method according to claim 1 wherein the step of storing incoming messages in a file having a horizontal file structure comprises the step of storing said messages in a flat file.

3. The method according to claim 2 wherein the step of performing a committing operation comprises the steps of:

committing the sequence numbers of the messages in the database when a committing operation of all updating operations is performed.

4. The method according to claim 3 wherein the step of performing a committing operation comprises the steps of:

checking the sequence number of said messages stored in said horizontal file structure;

using said sequence number to determine whether a predetermined number of messages has been received since a last operation of committing said updating operations in said database; and

if said predetermined number of messages has been received since a last operation of committing said updating operations in said database, performing said step of performing a committing operation.

5. The method according to claim 3 further comprising the step of:

registering the sequence numbers of all received messages stored in said flat file.

6. The method according to claim 5 further comprising the step of:

if said predetermined number of messages has been received, performing a committing operation of all updating operations according to the instructions of all messages accumulated in said file having a higher sequence number than the sequence number of said latest registered message.

7. The method according to claim 3 further comprising the step of:

performing a recovery operation in case of failure of said database and/or said server including the step of performing a committing operation of all updating operations according to the instructions of all messages accumulated in said file having a higher sequence number than the sequence number of said latest registered message.

8. The method according to claim 2 wherein the step of performing a committing operation comprises the step of:

performing a committing operation of all updating operations performed since said last committing operation at predetermined time intervals.

9. The method according to claim 1 wherein said step of performing a committing operation of all updating operations performed since said last committing operation comprises the steps of:

confirming that all operations has been committed; and

if not all operations have been committed, repeating said step of performing a committing operation of all updating operations performed since said last committing operation.

10. The method according to claim 9 wherein said step of performing a committing operation of all updating operations performed since said last committing operation comprises the step of:

registering the sequence number of the last message of said flat file.

11. A computer program product executable on a server in a computer system communicating with a plurality of clients, the server receiving incoming messages of the computer system, and being connected to a database for storing information according to instructions of the incoming messages, the computer program product causing the server to perform the steps of:

receiving updating instructions via incoming messages;

storing said incoming messages in a file having a horizontal file structure;

updating said database by performing updating operations according to said instructions of said messages; and

performing a committing operation of all updating operations performed since said last committing operation at predetermined intervals in order to make all data modifications performed since the start of the last committing operation a permanent part of the database.

12. The computer program product according to claim 11 wherein the computer program product causing the server to perform the step of storing said incoming messages in a file having a horizontal file structure comprises the computer program product causing the server to perform the step of storing incoming messages in flat file.

13. The computer program product of claim 12 wherein the computer program product causing the server to perform the step of performing a committing operation comprises the computer program product causing the server to perform the step of committing the sequence numbers of the messages in the database when a committing operation of all updating operations is performed.

14. The computer program product according to claim 13, wherein the computer program product causing the server to perform the step of performing a committing operation comprises the computer program product causing the server to perform the steps of:

checking the sequence number of said messages stored in said horizontal file structure;

using said sequence number to determine whether a predetermined number of messages has been received since a last operation of committing said updating operations in said database; and

if said predetermined number of messages has been received since a last operation of committing said updating operations in said database, performing said step of performing a committing operation.

15. A computer-readable medium that stores computer-executable process steps for receiving, processing, and storing messages coming to a computer system from a plurality of clients during system operation, the computer system including a server receiving incoming messages and being connected to a database for storing information according to instructions of said incoming messages, said computer-executable process steps causing the server to perform the steps of:

receiving updating instructions via incoming messages;

storing said incoming messages in a file having a horizontal file structure;

updating said database by performing updating operations according to said instructions of said messages; and

performing a committing operation of all updating operations performed since said last committing operation at predetermined intervals in order to make all data modifications performed since the start of the last committing operation a permanent part of the database.

16. The computer-readable medium according to claim 15 wherein said computer-executable process steps causing the server to perform the step of storing said incoming messages in a file having a horizontal file structure comprises said computer-executable process steps causing the server to perform the step of storing incoming messages in flat file.

17. The computer-readable medium of claim 16 wherein said computer-executable process steps causing the server to perform the step of performing a committing operation comprises said computer-executable process steps causing the server to perform the step of committing the sequence numbers of the messages in the database when a committing operation of all updating operations is performed.

18. The computer-readable medium according to claim 17 wherein said computer-executable process steps causing the server to perform the step of performing a committing operation comprises said computer-executable process steps causing the server to perform the steps of:

checking the sequence number of said messages stored in said horizontal file structure;

using said sequence number to determine whether a predetermined number of messages has been received since a last operation of committing said updating operations in said database; and

if said predetermined number of messages has been received since a last operation of committing said updating operations in said database, performing said step of performing a committing operation.