SQL Debugging: Locating Debugging Errors on the Server
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. |
If SQL debugging does not work, check the event log on the machine that is running SQL Server.
To locate SQL debugging errors in the event log
On the server machine, click Start, point to Settings, and click Control Panel.
In Control Panel, double-click the Administrative Tools folder.
In the Administrative Tools folder, double-click Event Viewer.
In the Event Viewer, look for errors whose source is listed as the SQL Server instance name, MSSQLSERVER, MSSQL$LEGACY, MSSQL$LEGACYIS, or, for SQL Server 2000, SQLDebugging98.
Double-click the event to read the Description in the Event Properties dialog box.
See Also
Reference
SQL Debugging Setup Errors and Troubleshooting