>The Windows account under which I'm running VS2005
>has the sysadmin role, and this is the same account that's
>used for the data connection.

> To use the SQL debugging, the application account must be a member of the
> sysadmin group in the target SQL Server being debugged, and the
> connection
> account also must be a member of the sysadmin role in the target SQL
> Server, please refer to the following MSDN documentation for details:

""Gary Chang[MSFT]"" <v-garych@online.microsoft.com> wrote in message
news:ciBWDpqBGHA.1236@TK2MSFTNGXA02.phx.gbl...
> Hi Paul,
>
>>The Windows account under which I'm running VS2005
>>has the sysadmin role, and this is the same account that's
>>used for the data connection.
>
> To use the SQL debugging, the application account must be a member of the
> sysadmin group in the target SQL Server being debugged, and the
> connection
> account also must be a member of the sysadmin role in the target SQL
> Server, please refer to the following MSDN documentation for details:
>
> How to: Set SQL Server Permissions for Debugging
> http://msdn2.microsoft.com/en-us/library/w1bhybwz.aspx
>
>
> By the way, the Windows XP Service Pack 2 and Windows 2003 have enhanced
> security features, remote debugging on Windows XP SP2 platforms requires
> some additional steps to configure the Windows Firewall. I suggest you may
> also take a look on the following doc:
>
> How to: Set Up Remote Debugging
> http://msdn2.microsoft.com/en-us/library/bt727f1t.aspx
>
>
> Thanks!
>
> Best regards,
>
> Gary Chang
> Microsoft Community Support
> --------------------
> Get Secure! ¡§C www.microsoft.com/security
> Register to Access MSDN Managed Newsgroups!
> http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
> &SD=msdn
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>

>Can I check - does "application account" mean the windows/domain
>account that I'm logged on as?

>This is the account I log onto Windows with, so it will be the account
>that VS2005 is running under.
>I am using this account (with Windows Authentication) for my Data
>Connection to the remote SQL Server 2005.
>This account has been added as a login to SQL Server, and has been
>granted the sysadmin role.
>(the account is also in the administrators group on both client & server)
>...
>The server is a virtual machine (VMware) - does that make any difference?

""Gary Chang[MSFT]"" <v-garych@online.microsoft.com> wrote in message
news:G8Bf69dEGHA.1240@TK2MSFTNGXA02.phx.gbl...
> Hi Paul,
>
>>Can I check - does "application account" mean the windows/domain
>>account that I'm logged on as?
>
> yes, you are right.
>
>>This is the account I log onto Windows with, so it will be the account
>>that VS2005 is running under.
>>I am using this account (with Windows Authentication) for my Data
>>Connection to the remote SQL Server 2005.
>>This account has been added as a login to SQL Server, and has been
>>granted the sysadmin role.
>>(the account is also in the administrators group on both client & server)
>>...
>>The server is a virtual machine (VMware) - does that make any difference?
>
> The server in a virtual machine shouldn't matter, I remote debug with a
> virtual machine's SQL server 2005 in our local domain, it works as
> expected. I think maybe there has some problem on the account setting in
> your virtual machine, does it also join the single domain which your
> working machine resides?
>
> I suggest you may test with the *sa* account of that virtual machine's SQL
> server 2005, you can use that sa account in the corresponding data
> connection.
>
>
> Thanks !
>
> Best regards,
>
> Gary Chang
> Microsoft Community Support
> --------------------
> Get Secure! ¡§C www.microsoft.com/security
> Register to Access MSDN Managed Newsgroups!
> http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
> &SD=msdn
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>