debugging local SQL Server stored procedures

server|sqlserver| Stored Procedures
Author:zfive5 (Zhaozidong)
email:zfive5@yahoo.com.cn

Recent work reasons write stored procedures, coding is unavoidable debugging, but SQL Server debugging of the Fool degree is simply not
Compared to Oracle, remember that when you were an Oracle project, everything was so simple when Pl/sql developer was installed.
, and now SQL Server needs to be able to debug and configure to ok!

Here is my practice:

First, if the debugging data on this machine, it's all very simple!

This is written in MSDN:

To enable stored procedure debugging on the SQL 2000 Desktop Engine, you must perform the following steps on the computer where the SQL 2000 Desktop Engine is installed.

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

Will MSSDI98. DLLs are copied from the Microsoft Visual Studio. NET 2003 Qlserver directory into the \binn directory.
Enable debugging with the SQL 2000 Desktop Engine (on a computer that does not have Visual Studio. NET installed)

Find MSSDI98 on the Visual Studio. NET CD or DVD. DLL and copy it to the \binn directory.
Find sqldbg on the Visual Studio. NET CD or DVD. DLL and copy it to the following directory:
Program Files\Common Files\Microsoft Shared QL debugging
Re-register the sqldbg by entering the following command at the command prompt. Dll:
regsvr32 sqldbg.dll
To grant the debugger user the Execute permission for the stored procedure sp_sdidebug:
GRANT EXECUTE
On Sp_sdidebug
To MyUserName


My steps:

1) regsvr32 sqldbg.dll
2) GRANT EXECUTE on sp_sdidebug to dbo

That's OK.

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


Now is still studying the database is not local situation, hope that other configuration successful people, say!