Export (0) Print
Expand All

T-SQL Database Debugging

This topic applies to:

Visual Studio Edition

Visual Basic

C#

C++

J#

Visual Web Developer

Express

No

No

No

No

No

Standard

No

No

No

No

No

Pro/Team

Yes

Yes

Yes

Yes

Yes

This section contains samples demonstrating debugging for all T-SQL database object types.

In the past, T-SQL developers often wrote and debugged their T-SQL applications by using the SQL Server Query Analyzer tool. Today, Query Analyzer has been replaced by the SQL Server Management Studio, which has no debugger. T-SQL developers now use the Visual Studio 2005 debugger instead.

Developers can also write their T-SQL applications in Visual Studio 2005, using a Database project. Whether you write your T-SQL application in Visual Studio 2005 or not, debugging procedures are almost identical.

There are three debugging scenarios to consider:

In order to debug a trigger, you must start your debugging session in a stored procedure. You cannot debug a stand-alone SQL script, have it fire a trigger, and be able to debug the trigger.

In This Section

Walkthrough: Debug a T-SQL Stored Procedure

Demonstrates how to debug stored procedures on a SQL Server.

Walkthrough: Debugging a T-SQL Trigger

Demonstrates how to step from a stored procedure into a trigger when it fires.

Walkthrough: Debugging a T-SQL User-Defined Function

Demonstrates how to step from a stored procedure into a user-defined function.

How to: Debug an Extended Stored Procedure

Creates an extended stored procedure and shows how to debug it.

See Also

Community Additions

ADD
Show:
© 2014 Microsoft