procedure timed out?

Last post 02-21-2009 1:25 PM by TATWORTH. 1 replies.

Sort Posts:

  • procedure timed out?

    02-18-2009, 2:54 PM
    • Participant
      969 point Participant
    • le9569
    • Member since 10-30-2002, 2:50 PM
    • Posts 256

    Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif";}

    Hello Experts,

    We currently have a procedure that pulls data from other databaselink.  This procedure takes quite a long time (2 hours+) to process and dump the data into one table.   The user gets the browser timed out.  Here are my questions:

     

    ·         What happens to the current procedure processing if the browser timed out or closed?   Is it still running or it drops right after the browser closed?

    ·         Is there a way to know if the proc is still running?

    ·         If that process is running, is there a way we can kill it?  By command line?

     

    Your guidance/help is truly appreciated. 

     

    le9569

     

    _____________________________________________

    live simply, love generously, care deeply, speak kindly
    Filed under: ,
  • Re: procedure timed out?

    02-21-2009, 1:25 PM
    • All-Star
      63,205 point All-Star
    • TATWORTH
    • Member since 02-04-2003, 8:34 AM
    • England
    • Posts 12,344
    • TrustedFriends-MVPs

     

    le9569:

    ·         What happens to the current procedure processing if the browser timed out or closed?   Is it still running or it drops right after the browser closed?

    ·         Is there a way to know if the proc is still running?

    ·         If that process is running, is there a way we can kill it?  By command line?

    The answer to question 2 and 3 is that you monitor the activity by putting a trace on the database from Sql Server Management Studio and having located the process id, kill the process. Regarding question 1, the process might continue. You can get a more expert answer by asking at:

     

    Don't forget to click "Mark as Answer" on the post that helped you.
    This credits that member, earns you a point and marks your thread as Resolved so we will all know you have been helped.
Page 1 of 1 (2 items)