API for programmatic retrieval and replay of database trace

• US 7,822,741 B2
• Filed: 06/21/2004
• Issued: 10/26/2010
• Est. Priority Date: 06/21/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Krassovsky, Viatcheslav, Balikov, Alexander G., Sonkin, Dmitry
• Primary Examiner(s): PANNALA, SATHYANARAYA R
• Application Number:
  US10/872,633
• Publication Number:
  US 20050283457A1
• Time in Patent Office: 2,318 Days
• Field of Search: 707/202, 707/102, 717/4, 717/139, 714 37- 39
• US Class Current: 707/718
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27

Abstract

Trace and replay objects can be designed to automatically perform operations concerning database trace data upon invocation by custom computer processes. Trace data can be saved to any of variety of locations. It can be manipulated for the purpose of storage or replay. Trace data can be played back against any database server using numerous replay configuration options. Replay notifications allow data to be changed just before it is submitted to a database for execution, and allow immediate examination of replay results and validation of playback correctness. Thus, trace and replay objects greatly simplify manageability of trace data. Custom processes can now completely automate security audit and health monitoring of traced database servers. Automatic verification of new server releases and security packs can also be performed. Custom processes can use the provided objects to flexibly access and manipulate the retrieval, storage, and replay of database trace data.

Claims

1. A system for supporting programmatic retrieval and replay of database trace data, said system comprising a processor configured to carry out instructions stored on computer readable media, said instructions comprising:

instructions for a first functional element for retrieving database trace data;

instructions for a first exposed function call whereby custom computer processes can programmatically initiate the operation of said first functional element;

instructions for a second functional element for storing database trace data;

instructions for a third functional element for replaying database trace data; and

instructions for a third exposed function call whereby custom computer processes can programmatically initiate the operation of said third functional element.

2. The system of claim 1, wherein said instructions for second functional element comprises instructions for storing database trace data one or more of a file, a table, and a server.

3. The system of claim 1, further comprising instructions for a fourth functional element for modifying stored database trace data.

4. The system of claim 3, further comprising instructions for a fourth exposed function call whereby custom computer processes can programmatically initiate the operation of said fourth functional element.

5. The system of claim 1, wherein said first functional element comprises one or more objects that inherit from an IDataReader interface.

6. The system of claim 1, wherein said instructions for a third functional element comprise instructions for notifying a custom computer process prior to replaying trace data.

7. The system of claim 1, wherein said instructions for a third functional element comprise instructions for notifying a custom computer process when database output from a replay is available for a custom computer process.

8. The system of claim 1, wherein said instructions for a third functional element comprise instructions for notifying a custom computer process when a replay is stopped.

9. The system of claim 1, wherein said instructions for a third functional element comprise instructions for a sequential replay mode in which substantially all database service requests for a particular database are replayed.

10. The system of claim 1, wherein said instructions for a third functional element comprise instructions for a connection level replay mode in which substantially all database service requests sent to a database from an identified client or set of clients are replayed.

11. The system of claim 1, wherein said instructions for a third functional element comprise instructions for gathering substantially all database output associated with a replay.

12. The system of claim 1, wherein said instructions for a third functional element comprise instructions for gathering substantially only reported database errors associated with a replay.