Transact-SQL Database Debugging
This topic applies to:
Visual Studio Ultimate |
Visual Studio Premium |
Visual Studio Professional |
Visual Studio Express |
|---|---|---|---|
.gif "ms165045.DoesApplybmp(en-us,VS.100).gif") |
|
|
.gif "ms165045.DoesNotApplybmp(en-us,VS.100).gif") |
This section contains walkthroughs demonstrating debugging for commonly used SQL Server database object types. These walkthroughs emphasize the use of Server Explorer to step into the Transact-SQL code of a database object. You can also debug Transact-SQL database objects with Visual Studio in the following ways:
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.
Developers using SQL Server beginning with SQL Server 2008 can also debug Transact-SQL objects by using the Database Engine Query Editor in SQL Server Management Studio. The Database Engine Query Editor beginning with SQL Server 2008 has debugging functionality similar to the Transact-SQL debugger in Visual Studio 2010.
In This Section
Walkthrough: Debug a Transact-SQL Stored Procedure
Demonstrates how to debug stored procedures on an instance of SQL Server.Walkthrough: Debugging a Transact-SQL Trigger
Demonstrates how to step from a stored procedure into a trigger when it fires.Walkthrough: Debugging a Transact-SQL User-Defined Function
Demonstrates how to step from a stored procedure into a user-defined function.Walkthrough: Debug an Extended Stored Procedure
Demonstrates how to debug an extended stored procedure.