Debug local SQL Server Stored Procedures

Author: zfive5 (zhaozidong)
Email: zfive5@yahoo.com.cn

The storage process is written for recent work, and debugging is inevitable during encoding. However, SQL Server debugging is not a dummies.
Compared to Oracle, remember that after PL/SQL developer is installed, everything is so simple
Single, And now SQL server needs to be able to debug the configuration before OK!

The following is my practice:

1. If the debugging data is on the local machine, everything is simple!

It is written in msdn as follows:

To enable Stored Procedure debugging on the SQL 2000 Desktop Engine, perform the following steps on the computer where the SQL 2000 Desktop Engine is installed.

Enable debugging with SQL 2000 Desktop Engine (on a computer with Visual Studio. NET installed)

Copy mssdi98.dll from the Microsoft Visual Studio. NET 2003/sqlserver directory to the/binn directory.
Enable debugging with SQL 2000 Desktop Engine (on a computer without Visual Studio. NET installed)

Find mssdi98.dll on Visual Studio. net cd or DVD and copy it to the/binn directory.
Find sqldbg. dll on Visual Studio. net cd or DVD and copy it to the following directory:
Program Files/common files/Microsoft shared/SQL debugging
Run the following command in the command prompt to register sqldbg. dll again:
Regsvr32 sqldbg. dll
Grant the execution permission of the stored procedure sp_sdidebug to the debugger User:
Grant Execute
On sp_sdidebug
To myusername

My steps:

1) regsvr32 sqldbg. dll
2) grant execute on sp_sdidebug to DBO

So OK.

See http://msdn.microsoft.com/library/CHS/vsdebug/html/vxlrfSettingUpSQLDebugging.asp

I am still studying the situation where the database is not local. I hope other people who have successfully configured the database will talk about it!