SQL Server 2005 T-SQL debugging alternatives

SQL Server 2005 T-SQL debugging alternatives

I recently read your response to the Query Analyzer having been replaced by the new SQL Server Management Studio. As it does not include a T-SQL debugger, what do you recommend as an alternative?

    Requires Free Membership to View

    Login

    When you register, you’ll also receive targeted emails from my team of award-winning editorial writers.  Our goal is to keep you informed on the hottest topics and biggest challenges faced by today's SQL Server database pros.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSQLServer.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSQLServer.com is governed by our Terms of Use. You may contact us at [email protected].

Unfortunately, you are correct: SQL Server Management Studio does not include the T-SQL debugger that was present in SQL Server Query Analyzer. Microsoft's solution is that developers wishing to debug T-SQL should use Visual Studio 2005, which does include a T-SQL debugger.

Personally, I am not a fan of step-debugging T-SQL at all. I find it a cumbersome process. The lack of visibility into temporary tables and table variables makes it less-than-ideal for most debugging scenarios I've encountered. I discussed some alternatives in an article Debugging with Macros and Assertions, which I wrote for SQL Server Professional magazine.

This was first published in June 2006

Back to top