A
Allen Smith
Is it possible to debug a stored procedure in SQL Server 2000 from VS 2003 ?
Thanks,
Smith
Thanks,
Smith
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
J
Joe Cool
Is it possible to debug a stored procedure in SQL Server 2000 from VS 2003 ?
Thanks,
Smith
Depends on what you mean by debug. You can trap SQL errors with a
Try/Catch structure and in the Catch you can display the SQL error
with the Exception.Method property.
E
Eric Moreau
Yes it's possible. See
http://msdn.microsoft.com/library/d...s/vsdebug/html/vxlrfsettingupsqldebugging.asp
--
HTH
Éric Moreau, MCSD, Visual Developer - Visual Basic MVP
(http://aspnet2.com/mvp.ashx?EricMoreau)
Conseiller Principal / Senior Consultant
Concept S2i inc. (www.s2i.com)
http://msdn.microsoft.com/library/d...s/vsdebug/html/vxlrfsettingupsqldebugging.asp
--
HTH
Éric Moreau, MCSD, Visual Developer - Visual Basic MVP
(http://aspnet2.com/mvp.ashx?EricMoreau)
Conseiller Principal / Senior Consultant
Concept S2i inc. (www.s2i.com)
T
Tom Dacon
Yes you can. Search the MSDN help file for 'debug stored procedure' and
you'll find everything you need to know.
Briefly, you right-click on the stored procedure from the server explorer,
and select 'step into stored procedure'. Once you're in, you are prompted
for any input parameters and then can step through the procedure. You have a
locals window, a watch window, and can set break points and so forth.
One thing you'll probably have to do manually is give yourself execute
permissions on the master.sp_sdidebug stored procedure, which you'll find in
the extended stored procedures section in Enterprise Manager.
So far I haven't found any way to leave a breakpoint in the stored procedure
and have it hit from application code. It doesn't look like it's possible.
Tom Dacon
Dacon Software Consulting
you'll find everything you need to know.
Briefly, you right-click on the stored procedure from the server explorer,
and select 'step into stored procedure'. Once you're in, you are prompted
for any input parameters and then can step through the procedure. You have a
locals window, a watch window, and can set break points and so forth.
One thing you'll probably have to do manually is give yourself execute
permissions on the master.sp_sdidebug stored procedure, which you'll find in
the extended stored procedures section in Enterprise Manager.
So far I haven't found any way to leave a breakpoint in the stored procedure
and have it hit from application code. It doesn't look like it's possible.
Tom Dacon
Dacon Software Consulting