Personally, I am not a fan of step-debugging T-SQL at all.
Requires Membership to View
To gain access to this and all member only content, please provide the following information:
By submitting your registration information to SearchSQLServer.com you agree to receive email communications from the TechTarget network of sites, and/or third party content providers that have relationships with TechTarget, based on your topic interests and activity, including updates on new content, event notifications, new site launches and market research surveys. Please verify all information and selections above. You may unsubscribe at any time from one or more of the services you have selected by editing your profile, unsubscribing via email or by contacting us here
- Your use of SearchSQLServer.com is governed by our Terms of Use
- We designed our Privacy Policy to provide you with important disclosures about how we collect and use your registration and other information. We encourage you to read the Privacy Policy, and to use it to help make informed decisions.
- 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.

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