Post reply

shrink fails with error - File ID of database ID cannot be shrunk as it is either being shrunk by another process or is empty

  • June 11, 2008 at 12:03 pm

    #129519

    This is an fyi (no response necessary).

    I got this error and researched it and found no good answer for how to deal with it:

    [font="Courier New"]"File ID 5 of database ID 8 cannot be shrunk as it is either being shrunk by another process or is empty"[/font]

    One post suggested that it was a memory issue, but it also suggested the only way to deal with it was to restart SQL. I don't have that luxury, so I cleared my cache and reran the shrink and the shrink worked.

    [font="Courier New"]

    DBCC DROPCLEANBUFFERS

    DBCC FREEPROCCACHE[/font]

    Thanks, Deb

    😎

  • June 11, 2008 at 1:21 pm

    #827485

    If Autoshrink is "ON" and you tried to run a "dbcc shrinkfile" you could get that message.


    * Noel

  • August 20, 2009 at 1:07 am

    #1041958

    See the Connect bug "DBCC SHRINKFILE and SHRINKDATABASE failing after backup" at

    http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=291408

  • March 16, 2010 at 5:28 pm

    #1134918

    One more thing to try that worked for me when I received this error message. I just increased the data file by a few MB and then tryed to do the Shrink again. It worked fine. It seems like adding a few MB to the data file resets an internal counter or switch that tells it it's not in the middle of a shrink now.

  • September 6, 2010 at 6:53 am

    #1216913

    thanks Ted, it worked for me as well....now to find out who is growing my tempdb 1 AM in the morning to rediculas sizes ..

  • October 13, 2010 at 9:13 am

    #1236296

    Thanks Ted. It works for me, too.:-)

  • November 8, 2010 at 8:51 am

    #1247703

    Whatta guy, Ted. Bailed me out also.

    Mike

    “I know that you believe you understand what you think I said, but I'm not sure you realize that what you heard is not what I meant.”...Robert McCloskey

    ___________________________________________________________________

  • March 19, 2011 at 9:36 am

    #1300921

    Thanks A lot Ted. This worked for me:-).

    Regards,

    Manjunath C Bhat,

    http://www.manjunathcbhat.in

    Thanks & Regards,
    Manjunath C Bhat,
    http://manjunathcbhat.blogspot.com,
    http://manjunathcbhat.wordpress.com

  • March 22, 2011 at 5:58 am

    #1301815

    More often than not, the best thing to do is to not shrink at all though.

    Kind regards,

    Vegard Hagen
    Norwegian DBA, occasional blogger and generally a nice guy who believes the world is big enough for all of us.
    @vegard_hagen on Twitter
    Blog: Vegards corner (No actual SQL stuff here - havent found my niche yet. Maybe some day...)

    It is better to light a candle than to curse the darkness. (Chinese proverb)

  • March 22, 2011 at 12:47 pm

    #1302104

    Thanks Ted - helped me too!

  • May 30, 2011 at 10:19 am

    #1331682

    Thanks Ted, it worked for me too.

  • July 5, 2011 at 3:57 am

    #1348151

    Me also faced the same issue.I increased some MB on the datafile and shrinked.It worked fine for me

  • July 5, 2011 at 7:15 am

    #1348257

    It worked for me also..

  • November 15, 2011 at 1:52 am

    #1407670

    For me too.. thanks

  • November 29, 2011 at 1:03 pm

    #1414308

    Thanks Ted, worked for me too

Viewing 15 posts - 1 through 15 (of 33 total)

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