SQL2K Stored Procedure Debugging broken with SP3
Sponsored By
Some folks have noticed that Stored Procedure Debugging was not working after applying SP3 to SQL Server 2000. If you run into this, the trick is to call
exec sp_sdidebug "legacy_on"This is a new security switch that was added in SP3 and only affects App Debugging. Also, note that the setting doesn't stick, and you'll need to call it each time you start up the SQL 2K Server.
About Scott
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
About Newsletter
Hosting By
February 18, 2003 23:49
Scott, thanks for the heads-up? I just sent a message to DM's CLR list right before reading your entry in NewsGator. Argh! My question was slightly different -- i can debug, but when I stop debugging (either detaching or closing the debugging session), SQL Server terminates. Do you know if this is a problem related to SP3, or just the VS.NET debugger attaching invasively? Thanks!
John St. Clair
John or Scott, did either of you get a resolution to this?
FYI: SP3a turned this off due to RPC restrictions for the Slammer Virus.
Eddy White
FYI: SP3a turned this off due to RPC restrictions for the Slammer Virus.
Eddy White
Comments are closed.