Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. Delete query stuck in suspended status

Delete query stuck in suspended status

Scheduled Pinned Locked Moved Database
databasecsharphelptutorialquestion
4 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • W Offline
    W Offline
    wizardzz
    wrote on last edited by
    #1

    I kicked off a Delete where value > 2 statement. I didn't expect it take take more than a couple of minutes, which has been the case for similar deletes on similar tables. But, it has been executing for 34 minutes, and when I run this statement, the status is suspended.

    SELECT start_time, status, command FROM sys.dm_exec_requests

    Any ideas as to how to check if or why the initial query is suspended or seemingly not running anymore. Edit: Using SQL '05, have seen some answers that suggest upgrading the SP2, but that is not an option right now. Could this be related to lack of space on the drive where the tempdb and masterdb are stored and the OS is running?

    Craigslist Troll: litaly@comcast.net "I have a theory that the truth is never told during the nine-to-five hours. " — Hunter S. Thompson

    W 1 Reply Last reply
    0
    • W wizardzz

      I kicked off a Delete where value > 2 statement. I didn't expect it take take more than a couple of minutes, which has been the case for similar deletes on similar tables. But, it has been executing for 34 minutes, and when I run this statement, the status is suspended.

      SELECT start_time, status, command FROM sys.dm_exec_requests

      Any ideas as to how to check if or why the initial query is suspended or seemingly not running anymore. Edit: Using SQL '05, have seen some answers that suggest upgrading the SP2, but that is not an option right now. Could this be related to lack of space on the drive where the tempdb and masterdb are stored and the OS is running?

      Craigslist Troll: litaly@comcast.net "I have a theory that the truth is never told during the nine-to-five hours. " — Hunter S. Thompson

      W Offline
      W Offline
      wizardzz
      wrote on last edited by
      #2

      Ok, it is a pageiolatch issue, lack of disk space.

      Craigslist Troll: litaly@comcast.net "I have a theory that the truth is never told during the nine-to-five hours. " — Hunter S. Thompson

      C 1 Reply Last reply
      0
      • W wizardzz

        Ok, it is a pageiolatch issue, lack of disk space.

        Craigslist Troll: litaly@comcast.net "I have a theory that the truth is never told during the nine-to-five hours. " — Hunter S. Thompson

        C Offline
        C Offline
        Chris Meech
        wrote on last edited by
        #3

        Only a computer programmer would make a delete operation fail because there is not enough space. :cool:

        Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra] posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]

        W 1 Reply Last reply
        0
        • C Chris Meech

          Only a computer programmer would make a delete operation fail because there is not enough space. :cool:

          Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra] posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]

          W Offline
          W Offline
          wizardzz
          wrote on last edited by
          #4

          Ugh, I had too much faith in the admin. I moved the files for my Database to the E drive with enough space. He had a C drive as the OS drive with only 12 gig, and a D drive that was, from my understanding, supposed to be for programs, including SQL. The clown admin installed SQL to the system C drive with very limited space. It turns out the temp table and log files were getting full, jamming up the OS/SQL D: drive. I should say that this definitely is not my fault, as I don't remote to the machine ever, just use SQL Server Management Studio. So there was no way for me to be worried about it, or know about it even.

          Craigslist Troll: litaly@comcast.net "I have a theory that the truth is never told during the nine-to-five hours. " — Hunter S. Thompson

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups