DBCC shrinkfile is taking over a day, should I kill it?

• boxta

  Ten Centuries

  Points: 1374

  More actions

  August 3, 2012 at 11:16 am

  #260081

  We had a 1TB DW that I did a bunch of archive / clean up / compress, and get it down to about 500GB

  So there was 500GB free space

  I did a DBCC Shrinkfile with 10% padding almost a day and a half ago, and it's still running!!!!

  When I query sys table it looks like it's 60% done. The DB file size is smaller, but not 400 GB smaller yet.

  should i let it keep running? or kill it?

  if i kill it, is it going to roll back for days too?

  Or if it rolls back.. is it going to at least keep the current progress (so db file is somewhat smaller)>?

• benjamin.reyes

  SSCertifiable

  Points: 5249

  More actions

  August 3, 2012 at 11:30 am

  #1521543

  You may want to look at column store indexes or just buying more drive space as an alternative.

  That shrink file command is probably being blocked (and fragmenting your indexes). Use sp_who2 or activity monitor to check.

  60% is greater than 40%, if you kill it it will probably take a very long time to roll back.