Post reply

DBCC SHRINKFILE

  • October 25, 2011 at 3:09 pm

    #390690

    Hi,

    The command does not seem to perform anything on one of our databases which is set to SIMPLE recovery model. Tried both DBCC SHRINKFILE with size and TRUNCATEONLY, neither option worked. The log filled up the entire space on the drive at this point.

    Anyone seen this before?

    Thanks

  • October 25, 2011 at 3:35 pm

    #1399354

    I assume you're trying to shrink the log file. Does it have free space in it? If not, shrink's going to do nothing (btw, TruncateOnly is an option only for the data file)

    Assuming it is the log file and there is no free space in the log file, have a read through this: http://www.sqlservercentral.com/articles/Transaction+Log/72488/

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • October 25, 2011 at 9:18 pm

    #1399399

    GilaMonster (10/25/2011)

    I assume you're trying to shrink the log file. Does it have free space in it? If not, shrink's going to do nothing (btw, TruncateOnly is an option only for the data file)

    Assuming it is the log file and there is no free space in the log file, have a read through this: http://www.sqlservercentral.com/articles/Transaction+Log/72488/

    Yes, trying to shrink the log. I think it was a long running active transaction that prevented me from shrinking it. Thanks for the article.

Viewing 3 posts - 1 through 2 (of 2 total)

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