Re: Visual Studio 2003 to SQl Server 2000

Tech-Archive recommends: Fix windows errors by optimizing your registry



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

"Allen Smith" <ASmith_Forest@xxxxxxxxxxx> wrote in message
news:#DdeiX6aFHA.3384@xxxxxxxxxxxxxxxxxxxxxxx
> Is it possible to debug a stored procedure in SQL Server 2000 from VS 2003
?
> Thanks,
> Smith
>
>


.



Relevant Pages

  • Re: Stored procedure Debug in .Net 2003
    ... > I am trying to debug a stored procedure using VS.Net 2003. ... > "Cannot debug stored procedures because the SQL server database is not ... > Database server is running on Win3K ... > debug stored procedure on local database that is running on ...
    (microsoft.public.dotnet.framework.adonet)
  • VS 2005, debug stored procedure
    ... I want to debug stored procedure, when I click on "Step Into ... Stored Procedure" in Server Explorer and enter input parameters ... ...
    (microsoft.public.vstudio.development)
  • Re: SPEED QUESTION
    ... The stored procedure could probably re-use the first result set's ... > can load the current month's data ... >> Tom Dacon ... >> Dacon Software Consulting ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Bizarre problem with ADO.Error
    ... in stored procedure use SET NOCOUNT ON ... looking in the locals window, the pCommand has an ActiveConnection property ... property returns 1 the first time it's called, but 0 after that - and only ...
    (microsoft.public.vb.general.discussion)
  • Re: Bizarre problem with ADO.Error
    ... in stored procedure use SET NOCOUNT ON ... looking in the locals window, the pCommand has an ActiveConnection property ... property returns 1 the first time it's called, but 0 after that - and only ...
    (microsoft.public.vb.database.ado)