Re: Remote SP debugging from VS 2003: error

I 'm still getting the error:

"Cannot debug stored procedures because the SQL Server database is not setup
correctly or user does not have permission to execute master.sp_sdidebug."

I have configured DCOM on the remote sql server according tothe MSDN
article.
I have added SQLDebugger account to default permissions in dcom.

I have also given full access to Master DB for the user
SQLDebugger and all stored procedures full access.

Does anybody have any idea why is it still giving the above error.

TIA
TS



.

Relevant Pages

  • Re: Remote SP debugging from VS 2003: error
    ... "Cannot debug stored procedures because the SQL Server database is not setup ... correctly or user does not have permission to execute master.sp_sdidebug." ... I have configured DCOM on the remote sql server according tothe MSDN ... I have added SQLDebugger account to default permissions in dcom. ...
    (microsoft.public.sqlserver.connect)
  • REmote Debugging from Visual Std. 2003 env
    ... "Cannot debug stored procedures because the SQL Server database is not setup ... correctly or user does not have permission to execute master.sp_sdidebug." ... I have configured DCOM on the remote sql server according tothe MSDN ... I have added SQLDebugger account to default permissions in dcom. ...
    (microsoft.public.sqlserver.clients)
  • help! report users permission on a SQL 2000 server
    ... stored procedures on each database. ... Is it possible to find permission using ... I read the online book of SQL server for 3 days. ...
    (microsoft.public.sqlserver.security)
  • Extreme performance issues (SQL Server 2000/ADO.NET/C#)
    ... This process runs very quickly if run through Query ... same exact stored procedures and views, run in the same exact order, through ... system that runs SQL Server (a 4-cpu Xeons system with 2gigs of physical ... When I execute these steps manually through query analyser,, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Securing Stored Procedures from being seen
    ... username, but in SQL Server, there are too many users to map an individuals ... granting the group execute permissions. ... but I would have to know what groups the user belongs ... see the names of any stored procedures to which he has no rights. ...
    (microsoft.public.sqlserver.security)