SQL CLR Database Debugging
This topic applies to:
Edition |
Visual Basic |
C# |
C++ |
Web Developer |
|---|---|---|---|---|
Express |
.gif "Topic does not apply") |
|
|
|
Standard |
|
|
|
|
Pro and Team |
.gif "Topic applies") |
|
|
|
Table legend:
|
Applies |
|
Does not apply |
.gif "Topic applies but command hidden by default") |
Command or commands hidden by default. |
This section contains samples for all CLR SQL database object types.
There are three different scenarios to consider:
Stepping into a SQL Server 2005 database object using Server Explorer. For more information, see How to: Step into an Object Using Server Explorer.
Running a test script using a Visual Studio 2005 SQL Server project.
Running an application that calls a stored procedure. For more information, see How to: Debug a SQL CLR Stored Procedure.
In order to debug a trigger, you must start your debugging session in a stored procedure. In particular, you cannot debug a stand-alone SQL script, nor can you debug a trigger by causing it to fire by invoking a script.
In This Section
How to: Debug a SQL CLR Stored Procedure
Demonstrates how to debug stored procedures on a SQL Server. Information includes connecting to a database, creating a stored procedure, stepping into a stored procedure, setting breakpoints, viewing parameters and local variables in the Locals window, and dragging variables from the Text editor into the Watch window.Walkthrough: Debugging a SQL CLR Trigger
Demonstrates how to step from a stored procedure into a trigger when it fires.Walkthrough: Debugging a SQL CLR User-Defined Scalar Function
Demonstrates how to step into a User Defined Function.Walkthrough: Debug a SQL CLR User-Defined Table-Valued Function
Demonstrates how to step into a User Defined Table-Valued Function.Walkthrough: Debugging a SQL CLR User-Defined Aggregate
Demonstrates how to step into a User Defined Aggregate.Walkthrough: Debugging a SQL CLR User-Defined Type
Demonstrates how to step into a User Defined Type.