Finding and profiling errors using the SQL Server's built-in error-finding device

Most developers are proud to claim that the code they write is not wrong, but in fact we all know that mistakes, both logically and physically, occur in the best projects. In other words, one of the most time-consuming tasks in the software development process is debugging. We've all tracked difficult errors, so most development kits include debugging tools to help find errors. Thanks to Microsoft for adding such a tool to the SQL Server environment starting with version 6.5. Let's take a closer look at this handy tool to see how to use it in everyday programming work.

Where is it?

SQL's "Server Debugging Interface" (SDI) can be entered from the Query Analyzer client. Find the stored procedure in the Query Analyzer Object Browser, see Figure A, and then right-click the name of the procedure you want to manipulate, and a menu pops up with the "Debug" option on the menu. Before you can use SDI, the SQL Server administrator must give you sufficient access, so check to make sure you have this permission.

Figure A

Query Analyzer provides stored procedure debug options