Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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 describes the software required for debugging the code in a SQL Server database. There are additional requirements when debugging a SQL Server multi-tier application. For more information, see Multi-tier Application Database Debugging.
Database Tier Software Requirements
SQL debugging with Microsoft Visual Studio 2005 requires the following software on the server:
Microsoft Windows 2000 or later is recommended.
SQL Server 2005 or SQL Server 2000 with Service Pack 3 required.
Database Tier Software Requirements (SQL CLR only)
SQL CLR debugging requires the following additional software on the server:
The Remote Debugging Monitor (msvsmon) is required to be running when you debug. If you are running SQL Server 2005 , the setup program to install msvsmon is already on the server, in <sql server install dir>\ 90\Shared\1033\rdbgsetup.exe. Run this program to install it, and SQL Server will launch it whenever you step into or hit a breakpoint.
All other requirements on this page apply to SQL CLR as well as TSQL.
Additional Multi-tier Software Requirements
With Visual Studio 2005, you can debug multi-tier applications that make connections to SQL Server databases and execute SQL stored procedures. To do this, the application tier must connect to the databases using one of the following:
SQL Client.
OLE DB, ODBC, or DBLIB.
A technology such as ADO or ADO.NET that is built on top of OLE DB or ODBC.
The managed data adapter for SQL Server.