I almost pointed you to that article yesterday but it said that the issue applies to Visual Studio versions earlier than Visual Studio.NET so I didn't think it would help.

At least I can help with automation. You can create a stored procedure to call sp_sdidebug and mark it for automatic execution. Then the stored procedure will be executed whenever SQL Server starts. You have to use T-SQL, EM doesn't let you set that option:

EXEC sp_procoption 'MyProc', 'startup', 'true'

To check whether a stored procedure is marked for startup execution, you can run this code:

SELECT OBJECTPROPERTY (object_id('MyProc'), 'ExecIsStartup')

Roman


>I found it!!!
>
>It is related so SP3 (of SQL Server).
>
>This is stated in "INF: T-SQL Debugger Is Turned Off By Default for Earlier Clients After You Install SQL Server 2000 Service Pack 3" from http://support.microsoft.com/default.aspx?scid=kb;en-us;Q328151 :
>
>
>Microsoft has disabled T-SQL Debugger for earlier clients for security reasons. To enable T-SQL Debugger for earlier clients, a member of the sysadmins server role, such as sa must explicitly enable debugging by running the following code:
> Exec sp_sdidebug 'legacy_on'
>
>You must repeat this procedure whenever you restart the server. Microsoft does not recommend that you use T-SQL Debugger on a production server.
>
>
>Now I need to find a way of automating this thing! I think I will write a small .sql file and use OSQL to run it every time I start my computer!
>
>
>
>>Eric,
>>
>>Did you by chance install SQL Server after VS.NET? If so then I would suggest running a VS.NET repair. I've seen where VS.NET needs to make some updates to your files when SQL Server is already installed.
>>
>>>I follow the steps from
>>>http://support.microsoft.com/default.aspx?scid=kb;[LN];316549 to debug
>>>stored procedures from VS.Net 2002 Enterprise Architect (with a local SQL
>>>Server 2000 SP3 ON XP Pro SP1) .
>>>
>>>I follow the steps of Option 1 and it executes exactly like it is written.
>>>
>>>I follow the steps of Option 2 and ... it doesn't work!
>>>
>>>When I start the application, I can see a white question mark on the
>>>breakpoint of the Stored Proc. The tooltip say:
>>>"The breakpoint will not currently be hit. Unable to bind SQL breakpoint at
>>>this time. Object containing the breakpoint is not loaded."
>>>
>>>Any ideas?