Remote Debugging Permissions
This topic applies to:
Visual Studio Edition |
Visual Basic |
C# |
C++ |
J# |
Web Dev |
Express |
No |
No |
No |
No |
No |
Standard |
No |
No |
No |
No |
No |
Pro/Team |
Yes |
Yes |
Yes |
Yes |
Yes |
The following permissions are required for remote debugging:
| Native Debugging |
|---|
To debug a process running under your account and password: No special permission needed. To debug a process running under another account name: Your Windows login account needs to be a member of the system administrators group on the remote machine. |
| Managed Debugging |
|---|
To debug a process running under your account and password: No special permission needed. To debug a process running under another account name: You need Administrator privilege on the remote machine. If the ASP.NET worker process aspnet_wp.exe is running as SYSTEM or ASPNET, for example, you need to be an administrator on the machine where that process is running. Processes that host the Common Language Runtime, such as SQL Server 2005, may enforce custom debugging privileges. |
| TSQL (versions prior to SQL Server 2005) |
|---|
You must have permission to execute sp_sdidebug() on the SQL2000 or SQL7 database. On operating systems before Windows XP, SQL Server must not be running as Local System. |
| SQL Server 2005 |
|---|
Your Windows user account on both the application machine and the SQL Server needs to be a member of SQL Server's sysadmin group. For more information see How to: Set SQL Server Permissions for Debugging. |