Author: zfive5 (zhaozidong) email: zfive5@yahoo.com.cn
Recently, the work is written in the stored procedure, and it is inevitably debugged when encoding. However, the degree of fools in SQL Server debugging cannot be comparable to Oracle, and it is as good as the Oracle project, as long as PL / SQL developer, everything is so simple, and Now SQLServer wants to debug and need to configure the configuration to be OK!
Here is my practice:
First, if the debug data is in this machine, it is very simple!
This is written in MSDN:
To enable storage procedure debug on the SQL 2000 desktop engine, you must perform the following steps on your computer that installs the SQL 2000 desktop engine.
Enable debugging using the SQL 2000 desktop engine (on a computer installed in Visual Studio .NET)
Copy MSSDI98.DLL from the Microsoft Visual Studio .NET 2003 / SQLServer directory to the / binn directory. Enable debugging using the SQL 2000 desktop engine (on a computer that does not have Visual Studio .NET)
Find the MSSDi98.dll on the Visual Studio .NET CD or DVD and copy it to the / binn directory. Find sqldbg.dll on the Visual Studio .NET CD or DVD and copy it to the following directory: Program files / common files / microsoft shared / sql debugging Re-registration SQLDBG.dll: regsvr32 sqldbg.dll by entering the following command at the command prompt: regsvr32 sqldbg.dll Permission to the debugger user to the execution permission of 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
This is OK.
See: http://msdn.microsoft.com/library/chs/vsdebug/html/vxlrfsettingupsqldebugging.asp
Now I am also studying the database is not a local situation, I hope other people who have successfully configured!
