How to: Set Permissions for Debugging on SQL Server 2000
[This documentation is for preview only, and is subject to change in later releases. Blank topics are included as placeholders.]
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. |
To debug on a SQL Server 2000, you must have permission to execute the extended stored procedure sp_sdidebug. You must also own any stored procedures you want to debug.
To grant permission to execute the extended stored procedure sp_sdidebug, you can use the Enterprise Manager, which ships with SQL Server 2000, or consult your database administrator.
The following code shows an example of how to grant sdidebug permission to a user:
EXEC sp_grantlogin 'mydomain\myusername'
EXEC sp_grantdbaccess ' mydomain\myusername', 'Myname'
GRANT EXEC ON sp_sdidebug TO Myname
in database 'master'
For Windows NT 4.0 only, you must perform the following steps.
Note
The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. To change your settings, choose Import and Export Settings on the Tools menu. For more information, see Working with Settings.
To set up SQL Server 2000 for debugging for Windows NT 4.0
On the Start menu, click Settings, and then click Control Panel.
In Control Panel, click Services.
Select MSSQLServer, and then click Startup.
Select the Log On As check box. If the option is set to System Account, change it to This Account, type the valid domain and user account in the form domain\account, of a user with administration privileges, such as the administrator on the local SQL Server machine, and then enter the password.
If you have changed the settings, restart SQL Server.