RE: Stepping into a SQL Server 2000 stored procedure

Hi Alfred,

Welcome to MSDN newsgroup!

I have performed the test from your description. All seems work well. There
is one thing need to be paid attention is you should execute the stored
procedure for your database as below:
exec sp_sdidebug 'legacy_on'

Additionally, I suggest you can debug the stored procedure by using SQL
Query Analyzer if you can not debug it in VS.NET. This will help me to
narrow down the current issue. Thanks for your understanding! I'm looking
forward your reply!

Regards,

Yuan Ren [MSFT]
Microsoft Online Support

.

Relevant Pages

  • Re: SQLdatasource delete with parameter output
    ... Also you can possibly debug and step into your stored procedure. ... @SiteProjectID Int, ... @MeasureID Int, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: OPENXML debugging
    ... I am a bit confused re your debug feedback. ... > The code then called the stored procedure - again, ... I did turn on T-SQL debugging when the throw was ... > If the work around is the best practice, can the MSDN article be changed? ...
    (microsoft.public.sqlserver.xml)
  • Re: ERROR 8162
    ... can't help since I am not able to debug it. ... > I not using a Stored Procedure. ... > from within an SQR program. ... >, JOBCODE ...
    (microsoft.public.sqlserver.programming)
  • Re: VS .NET Debugging
    ... Web interface: ... However do not know it anymore, maybe you can search it yourself. ... Start debug and I ... > and of course while the stored procedure does execute and return results, ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Unable to debug SQL from within the .NET IDE
    ... Given an application that uses a SQL Server stored procedure that is causing ... Use Visual Studio .NET to debug SQL Server stored procedures (in both ... Debugging a stored procedure in standalone mode ...
    (microsoft.public.dotnet.framework.adonet)
Loading