SQL server debugging

• US 20050193264A1
• Filed: 02/10/2004
• Published: 09/01/2005
• Est. Priority Date: 02/10/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Winn, Daniel Hunter, Bendixen, Mason, Khan, Azeemullah
• Granted Patent: US 7,500,225 B2
• Time in Patent Office: Days
• US Class Current: 714/38.14
• CPC Class Codes: G06F 11/362 Software debugging

Abstract

A software architecture for debugging the execution of T-SQL and managed data-tier application logic associated with a single connection, in isolation from other connections, is provided. In the architecture, a database server hosts the data-tier application logic. A client connects to the database server and issues requests on the connection, which initiates the execution of the data-tier application logic. A debugger debugs a client process on the server. An application program interface (API) receives a request to initiate a debugging session from the debugger, and returns an interface pointer to the debugger, thereby enabling the debugger to debug the client connection to the server.

Claims

1. A software architecture for debugging a distributed database application process on a client connection, comprising:

a server, wherein the server runs the distributed database application;

a client, wherein the client interacts with the distributed database application by way of the client connection;

a debugger, wherein the debugger debugs the distributed database application process; and

an application program interface (API), wherein the API receives a request to initiate a debugging session from the debugger, returns an interface pointer to the debugger, causes the server to the client connection according to the interface pointer, and connects the client connection to the debugger.

2. The software architecture of claim 1, wherein the server, client and debugger are operating on the same computer.

3. The software architecture of claim 1, wherein the server and debugger are operating on the same computer.

4. The software architecture of claim 1, wherein the server and debugger are operating on different computers.

5. The software architecture of claim 4, wherein the API receives a debugger request to debug managed code, causes the server to call a remote debugging component, and wherein the debugger debugs the managed code by way of the remote debugging component.

6. The software architecture of claim 1, wherein the API further detects a transition between Transact-Structured Query Language (T-SQL) and managed code and calls a method to communicate the transition to the debugger.

7. The software architecture of claim 6, wherein the debugger debugs the distributed application process according to the transition.

8. The software architecture of claim 1, wherein the debugger further comprises a user interface, wherein the user interface displays only the T-SQL activity within the server on the client connection being debugged.

9. The software architecture of claim 1, wherein the debugger further comprises a user interface, wherein said user interface displays only threads associated with the client connection.

10. The software architecture of claim 1, wherein the server detects an addition of a dynamic T-SQL frame to a user stack within the server and calls a method to pass text of the dynamic T-SQL frame to the debugger.

11. A method of communicating between a server process, a client process and a debugger process in a distributed database environment, comprising:

receiving a first call for a stored procedure from the debugger process;

returning an interface pointer to the debugger process responsive to the received first call;

receiving a second call for a register method from the debugger process, wherein the second call comprises a machine name, a process ID and an interface pointer;

recognizing a client connection matching the machine name, process ID and interface pointer on the server process;

halting execution of the client connection on the server process responsive to said detection;

executing a third call, wherein the third call establishes operative communications between the debugger process and the client process; and

debugging the client process.

12. The method of claim 11, wherein the third call uses the interface pointer received in the second call.

13. The method of claim 11, further comprising:

detecting a request from the debugger process to debug managed code;

calling a remote debugging component; and

debugging the managed code by way of the remote debugging component.

14. The method of claim 11, further comprising detecting a transition between Transact-Structured Query Language (T-SQL) and managed code on the client connection;

and calling a method to communicate the transition to the debugger process.

15. The method of claim 14, further comprising debugging the client connection according to the transition.

16. The method of claim 11, wherein the server process is executing T-SQL code on the client connection and the debugger process is debugging the T-SQL code, and further comprising displaying, on a user interface, only the T-SQL code executed by the server process on the client connection being debugged.

17. The method of claim 11, wherein the server process is executing managed code on the client connection and the debugger process is debugging the managed code, and further comprising displaying, on a user interface, only threads associated with the managed code being debugged.

18. The method of claim 11, further comprising detecting an addition of a dynamic T-SQL frame to a user stack within the server process and calling a method to pass text of the dynamic T-SQL frame to the debugger process, and wherein debugging the client process is by way of the text of the dynamic T-SQL frame.

19. A computer-readable medium having computer-executable instructions for performing a method of communicating between a server process, a client process and a debugger process in a distributed database environment, the method comprising:

receiving a first call for a stored procedure from the debugger process;

returning an interface pointer to the debugger process responsive to the received first call;

receiving a second call for a register method from the debugger process, wherein the second call comprises a machine name, a process ID and an interface pointer;

recognizing a client connection matching the machine name, process ID and interface pointer on the server process;

halting execution of the client connection on the server process responsive to said detection;

executing a third call, wherein the third call establishes operative communications between the debugger process and the client process; and

debugging the client process.

20. The computer-readable medium of claim 19, wherein the third call uses the interface pointer received in the second call.

21. The computer-readable medium of claim 19, wherein the method further comprises:

detecting a request from the debugger process to debug managed code;

calling a remote debugging component; and

debugging the managed code by way of the remote debugging component.

22. The computer-readable medium of claim 19, wherein the method further comprises detecting a transition between Transact-Structured Query Language (T-SQL) and managed code on the client connection;

and calling a method to communicate the transition to the debugger process.

23. The computer-readable medium of claim 22, wherein the method further comprises debugging the client connection according to the transition.

24. The computer-readable medium of claim 19, wherein the server process is executing T-SQL code on the client connection and the debugger process is debugging the T-SQL code, and wherein the method further comprises displaying, on a user interface, only the T-SQL code executed by the server process on the client connection being debugged.

25. The computer-readable medium of claim 19, wherein the server process is executing managed code on the client connection and the debugger process is debugging the managed code, and wherein the method further comprises displaying, on a user interface, only threads associated with the managed code being debugged.

26. The computer-readable medium of claim 19, wherein the method further comprises detecting an addition of a dynamic T-SQL frame to a user stack within the server process and calling a method to pass text of the dynamic T-SQL frame to the debugger process, and wherein debugging the client process is by way of the text of the dynamic T-SQL frame.

27. A method of initiating a debugging session between a debugger and a client connection on a server running a distributed database application, comprising:

specifying the client connection to be debugged by way of an API;

returning an interface pointer to the debugger by way of the API;

calling a register method, wherein the register method uses the interface pointer to detect the client connection associated with the interface pointer;

halting execution of the client connection; and

enabling the debugger to debug the client connection by way of the server and the API.

28. The method of claim 27, further comprising debugging the client connection.

29. The method of claim 27, further comprising returning a machine name and process identifier to the debugger by way of the API.

30. The method of claim 27, further comprising detecting a security context of the client connection and performing said connecting step only if the security context matches a predetermined security context.

31. The method of claim 27, wherein said calling step is by way of a distributed component object model (DCOM).

32. A computer-readable medium having computer-executable instructions for performing a method of initiating a debugging session between a debugger and a client connection on a server running a distributed database application, the method comprising:

specifying the client connection to be debugged by way of an API;

returning an interface pointer to the debugger by way of the API;

calling a register method, wherein the register method uses the interface pointer to detect the client connection associated with the interface pointer;

halting execution of the client connection; and

enabling the debugger to debug the client connection by way of the server and the API.

33. The computer-readable medium of claim 32, wherein the method further comprises debugging the client connection.