Re: Error message with stored procedure

Forgot to say - a good way to troubleshoot something like this is to use SQL
Profiler to see what SQL statements actually get submitted.

Plamen Ratchev
http://www.SQLStudio.com


.

Relevant Pages

  • Re: Wierd error
    ... morning thousands of SQL statements would have been processed. ... Jon ... > People seem to neglect my favourite tools in SQL, profiler. ... (SQL2000 and ASP). ...
    (microsoft.public.inetserver.asp.general)
  • Re: Wierd error
    ... morning thousands of SQL statements would have been processed. ... Jon ... > People seem to neglect my favourite tools in SQL, profiler. ... (SQL2000 and ASP). ...
    (microsoft.public.sqlserver.programming)
  • Re: Wierd error
    ... Microsoft does have post-mortem debugger tools that you can attach to your ... > Unfortunately it seems theses errors occur way late in the evening and by ... > morning thousands of SQL statements would have been processed. ... >> People seem to neglect my favourite tools in SQL, profiler. ...
    (microsoft.public.inetserver.asp.general)
  • Re: Wierd error
    ... Microsoft does have post-mortem debugger tools that you can attach to your ... > Unfortunately it seems theses errors occur way late in the evening and by ... > morning thousands of SQL statements would have been processed. ... >> People seem to neglect my favourite tools in SQL, profiler. ...
    (microsoft.public.sqlserver.programming)
  • Re: searching for cause of deadlock
    ... John ... we're getting output from trace 1204 et al but it doesn't show ... > the sql statements that are causing the deadlock, ... >> look at using profiler to detect this. ...
    (microsoft.public.sqlserver.tools)