Post reply

How to debug a SP in Client/Server

  • June 21, 2005 at 9:03 pm

    #164983

    I have some SP which fail occassionally in productions, due to doggy data. What is the easiest way to find out the line that failed? I tried putting some 'print' statement there but cannot find the output when the SP is lauched by client, ie. not from QA.

    Thanks in advance.

    James

  • June 21, 2005 at 9:35 pm

    #567297

    Best bet is to change your Print statements to insert the text into a logging table.

     

    --------------------
    Colt 45 - the original point and click interface

  • June 21, 2005 at 9:51 pm

    #567301

    I usually just set a breakpoint where the sp is being called (vb 6) and take all the parameter values and run it in QA...works quickest and easiest for me!!!







    **ASCII stupid question, get a stupid ANSI !!!**

  • June 23, 2005 at 6:23 am

    #567856

    Or do a trace... Tracing SP:StmtStarting and SP:StmtCompleted gives quite a good understanding what was being done in the SP...

    Tracing puts a little load on the server, but then again, if you heavily are debugging in Production I guess your debugging might consume more resources then a well planned/configured trace 

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply