SQL Debugging: Security Issues
This topic applies to:
Edition |
Visual Basic |
C# |
C++ |
Web Developer |
---|---|---|---|---|
Express |
![]() |
![]() |
![]() |
![]() |
Standard |
![]() |
![]() |
![]() |
![]() |
Pro and Team |
![]() |
![]() |
![]() |
![]() |
Table legend:
![]() |
Applies |
![]() |
Does not apply |
![]() |
Command or commands hidden by default. |
SQL debugging uses DCOM to communicate between server and client. You need appropriate permissions to be able to debug against the SQL Server. If you get a message box saying that security has not been set up correctly on a server, check for the following:
- Proper access privileges on the machine running SQL server. For more information, see How to: Configure DCOM for SQL Server 2000 Debugging.
See Also
Reference
SQL Debugging Setup Errors and Troubleshooting