API for programmatic retrieval and replay of database trace

• US 20050283457A1
• Filed: 06/21/2004
• Published: 12/22/2005
• Est. Priority Date: 06/21/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sonkin, Dmitry, Krassovsky, Viatcheslav, Balikov, Alexander G.
• Granted Patent: US 7,822,741 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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, comprising:

a first functional element comprising a plurality of machine readable instructions for retrieving database trace data;

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

a second functional element comprising a plurality of machine readable instructions for storing database trace data;

a third functional element comprising a plurality of machine readable instructions for replaying database trace data; and

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 second functional element comprises a plurality of machine readable 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 a fourth functional element comprising a plurality of machine readable instructions for modifying stored database trace data.

4. The system of claim 3, further comprising 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 third functional element comprises a plurality of machine readable instructions for notifying a custom computer process prior to replaying trace data.

7. The system of claim 1, wherein said third functional element comprises a plurality of machine readable 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 third functional element comprises a plurality of machine readable instructions for notifying a custom computer process when a replay is stopped.

9. The system of claim 1, wherein said third functional element comprises a plurality of machine readable 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 third functional element comprises a plurality of machine readable 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 third functional element comprises a plurality of machine readable instructions for gathering substantially all database output associated with a replay.

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

13. A method for allowing a computerized process to programmatically retrieve and replay database trace data, comprising:

exposing a first function call for retrieving database trace data, wherein said first function call is exposed to custom computerized processes;

retrieving database trace data in response to invoking said first function call;

storing database trace data in a location specified by one or more of said custom computerized processes or in a location specified as a default location;

exposing a second function call for replaying database trace data, wherein said second function call is exposed to custom computerized processes; and

replaying database trace data in response to invoking said second function call.

14. The method of claim 13, wherein said storing comprises writing database trace data to one or more of a file, a table, and a server.

15. The method of claim 13, wherein said function call for retrieving comprises a plurality of function calls which operate to store database trace data in a plurality of locations, whereby a storage location can be specified by custom computerized processes by invoking one or more of the plurality of function calls.

16. The method of claim 13, further comprising exposing a fourth function call for modifying database trace data, wherein said fourth function call is exposed to custom computerized processes.

17. The method of claim 16, further comprising modifying database trace data in response to invoking said fourth function call.

18. The method of claim 13, wherein said retrieving database trace data involves one or more objects that inherit from an IDataReader interface.

19. The method of claim 13, further comprising notifying a custom computer process prior to replaying trace data.

20. The method of claim 19, wherein notifying comprises returning an event object to a custom computer process.

21. The method of claim 19, wherein notifying comprises returning a delegate to a custom computer process.

22. The method of claim 19, wherein notifying comprises returning an interface to a custom computer process, wherein said interface defines parameters for modifying trace data records.

23. The method of claim 19, wherein notifying comprises returning an interface to a custom computer process, wherein said interface defines parameters for skipping trace data during said replaying.

24. The method of claim 13, further comprising notifying a custom computer process when database output from a replay is available for a custom computer process.

25. The method of claim 24, wherein notifying comprises returning an event object to a custom computer process.

26. The method of claim 24, wherein said notifying comprises returning a delegate to a custom computer process.

27. The method of claim 13, wherein replaying comprises notifying a custom computer process when a replay is stopped.

28. The method of claim 13, wherein said replaying comprises connecting to a database, wherein the database is specified by a custom computer process.

29. The method of claim 13, wherein said replaying comprises controlling a size of a thread pool, wherein said thread pool size is specified by a custom computer process.

30. The method of claim 13, wherein said replaying comprises controlling a time interval which one or more elements in the system for supporting programmatic retrieval and replay of database trace data will wait prior to terminating a process that is not progressing.

31. The method of claim 13, wherein said replaying comprises controlling polling frequency for discovering processes that are not progressing.

33. The method of claim 13, wherein said replaying comprises utilizing a sequential replay mode in which substantially all database service requests for a particular database are replayed.

34. The method of claim 13, wherein said replaying comprises utilizing 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.

35. The method of claim 13, wherein said replaying comprises gathering substantially all database output associated with a replay.

36. The method of claim 13, wherein said replaying comprises gathering substantially only reported database errors associated with a replay.

32. (canceled)

37. A computer readable medium bearing instructions for allowing a computerized process to programmatically retrieve and replay database trace data, comprising:

instructions for exposing a first function call for retrieving database trace data, wherein said first function call is exposed to custom computerized processes;

instructions for retrieving database trace data in response to invoking said first function call;

instructions for storing database trace data in a location specified by one or more of said custom computerized processes or in a location specified as a default location;

instructions for exposing a second function call for replaying database trace data, wherein said second function call is exposed to custom computerized processes; and

instructions for replaying database trace data in response to invoking said second function call.

38. A computer readable medium according to claim 37, wherein said instructions for storing comprise instructions for writing database trace data to one or more of a file, a table, and a server.

39. A computer readable medium according to claim 37, wherein said instructions for exposing a first function call for retrieving comprises instructions for a plurality of function calls which operate to store database trace data in a plurality of locations, whereby a storage location can be specified by custom computerized processes by invoking one or more of the plurality of function calls.

40. A computer readable medium according to claim 37, further comprising instructions for exposing a fourth function call for modifying database trace data, wherein said fourth function call is exposed to custom computerized processes.

41. A computer readable medium according to claim 40, further comprising instructions for modifying database trace data in response to invoking said fourth function call.

42. A computer readable medium according to claim 37, wherein said instructions for retrieving database trace data comprise one or more objects that inherit from an IDataReader interface.

43. A computer readable medium according to claim 37, further comprising instructions for notifying a custom computer process prior to replaying trace data.

44. A computer readable medium according to claim 43, wherein instructions for notifying comprise instructions for returning an event object to a custom computer process.

45. A computer readable medium according to claim 43, wherein said instructions for notifying comprise instructions for returning an interface to a custom computer process, and wherein said interface defines parameters for modifying trace data.

46. A computer readable medium according to claim 43, wherein said instructions for notifying comprise instructions for returning an interface to a custom computer process, wherein said interface defines parameters for skipping trace data during said replaying.

47. A computer readable medium according to claim 43, wherein instructions for notifying comprise instructions for returning a delegate to a custom computer process.

48. A computer readable medium according to claim 37, further comprising instructions for notifying a custom computer process when database output from a replay is available for a custom computer process.

49. A computer readable medium according to claim 48, wherein instructions for notifying comprise instructions for returning an event object to a custom computer process.

50. A computer readable medium according to claim 48, wherein said instructions for notifying comprise instructions for returning a delegate to a custom computer process.

51. A computer readable medium according to claim 37, wherein said instructions for replaying comprise instructions for notifying a custom computer process when a replay is stopped.

52. A computer readable medium according to claim 37, wherein said instructions for replaying comprise instructions for connecting to a database, wherein the database is specified by a custom computer process.

53. A computer readable medium according to claim 37, wherein said instructions for replaying comprise instructions for utilizing a sequential replay mode in which substantially all database service requests for a particular database are replayed.

54. A computer readable medium according to claim 37, wherein said instructions for replaying comprise instructions for utilizing 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.

55. A computer readable medium according to claim 37, wherein said instructions for replaying comprise instructions for gathering substantially all database output associated with a replay.

56. A computer readable medium according to claim 37, wherein said instructions for replaying comprise instructions for gathering substantially only reported database errors associated with a replay.