Debugging Transact-SQL Database Objects

This topic applies to:

Visual Studio Ultimate	Visual Studio Premium	Visual Studio Professional	Visual Studio Express

Debugging Transact-SQL code can be done several ways:

Existing database objects can be debugged using Visual Studio outside of any project. Using Server Explorer, you can step into a database object. For more information, see How to: Step into an Object Using Server Explorer.
New Transact-SQL scripts or existing database objects can be debugged using the Visual Studio SQL Server Database project or SQL Server Server project type. For more information, see How to: Debug with a SQL Server Database Project or Server Project.
Existing database objects that are called by application code in C++, Visual Basic, or C# projects can be debugging using the Server Explorer data connection. For more information, see Debugging Multi-tier Database Applications.

In This Section

Overview of Visual Database Tools
Describes limitations of using Transact-SQL debugging features.
Common Procedure Reference (Debugging Transact-SQL)
Describes procedures that occur in many different scenarios and samples.
Transact-SQL Database Debugging
Shows how to debug various kinds of Transact-SQL database objects: stored procedures, triggers, user-defined functions, and extended stored procedures.

Setting Up Transact-SQL Debugging
Lists software requirements for Transact-SQL debugging (for the server and workstation), instructions for enabling Transact-SQL debugging, installing, configuring, and troubleshooting setup.
Debugging Multi-tier Database Applications
Describes the necessary setup procedures, and provides a sample that shows how to debug a multi-tiered database application.
SQL CLR Database Debugging
Describes debugging SQL CLR database objects.
Using the Transact-SQL Debugger
Describes debugging Transact-SQL database objects with SQL Server Management Studio.