|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
How to: Debug Database Objects
A database unit test consists of the following:
One or more test conditions, which are written in C# or Visual Basic. To debug test conditions, follow the procedure for debugging a unit test as described in How to: Debug while a Test is Running.
One or more (Transact-SQL) T-SQL scripts that run on objects in the database that you are testing. You cannot debug these T-SQL scripts.
The procedures in this topic describe how to debug particular database objects, such as stored procedures, functions, and triggers. To debug a database object, follow these procedures in this order:
Enable SQL Server debugging on your test project.
Add breakpoints to your T-SQL script.
Debug your database unit test. In this procedure, you run the test in debug mode.
To enable SQL Debugging on your test project
Open Solution Explorer.
In Solution Explorer, right-click the test project, and click Properties.
A properties page that has the same name as the test project opens.
On the properties page, click Debug.
Under Enable Debuggers, click Enable SQL Server debugging.
Save your changes.
To set the execution context timeout to enable debugging for your test project
On the File menu, point to Open, and click File.
Browse to the folder that contains your test project, and double-click the app.config file.
The app.config file opens in the editor.
Modify the ExecutionContext node to add a command timeout, as in the following example:
<ExecutionContext CommandTimeout ="300" Provider="System.Data.SqlClient" ConnectionString="Data Source=TargetServerName\TargetInstanceName;Initial Catalog=TargetDatabaseName;Integrated Security=True;Pooling=False" />
Save your changes.
Rebuild your database unit test project.
If you do not rebuild your project, the changes that you made to app.config will not be applied when you run your database unit tests, and debugging will fail.
To add breakpoints to your T-SQL script
On the View menu, open Server Explorer.
Under Data Connections, expand the node of the database that you want to test.
If a small red 'x' appears next to the icon of the database, the connection to the database is closed. In this case, right-click the database, and click Refresh. You might have to supply credentials to open the connection to the database.
Expand the Views, Stored Procedures, or Functions node to find the object that you want to debug.
Double-click the object that you want to debug.
Click the gray sidebar to set a breakpoint.
To debug your database unit test
Open the Test View window.
Click the test whose T-SQL script exercises the database object in which you set breakpoints.
On the toolbar of the Test View window, click Debug Selection.
The test runs in debug mode until a breakpoint in the database object is encountered.
(Optional) To open another debug window, open the Debug menu, point to Windows, and click Breakpoints, Output, or Immediate.