Results 1 to 5 of 5
  1. #1
    Join Date
    Dec 2007
    Posts
    288

    Unanswered: KILL EXEC sp_delete_backuphistory '12/31/07'

    SQL Server 2000 with 32 Databases

    I started

    EXEC sp_delete_backuphistory '12/31/07'

    about an hour ago and the Server is at a crawl.

    How do I go about killing this ???????

  2. #2
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    Use sp_who2 to find the offending spid and then use KILL command. BTW - this is the last, last alternative - right?

    The sproc is notoriously slow. Tara wrote an alternative:
    http://weblogs.sqlteam.com/tarad/arc...from-msdb.aspx
    Testimonial:
    pootle flump
    ur codings are working excelent.

  3. #3
    Join Date
    Dec 2007
    Posts
    288
    last alternative?? I don't know what you mean.... My server is at a crawl and I can't open any apps that connect to it... is there something else I can try??

  4. #4
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    Quote Originally Posted by itsonlyme44
    is there something else I can try??
    Waiting. If it is not an option for you then it is not an option. However, killing a process that is running DML on system tables is something I would be very hesitant to do without knowing exactly what sort of state the database will be left in.

    It is your server - you know your parameters better than I.
    Testimonial:
    pootle flump
    ur codings are working excelent.

  5. #5
    Join Date
    Dec 2007
    Posts
    288
    Thank you so much. I am waiting for now ...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •