Post reply

transaction log eats up all the space and growing until sql is stopped

  • November 26, 2013 at 10:32 pm

    #1669330

    Yes' Got the culprit, you're right.

    Its the vmware stored procedure. Ah!

    Thanks..

  • November 27, 2013 at 12:02 am

    #1669342

    If it's leaving a transaction open, I suspect the procedure's failing somewhere or has something else wrong.

    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

  • November 27, 2013 at 6:19 pm

    #1669607

    Yes, they, the vendor have released couple of patches/workarounds to address those issues. Thanks.

  • December 12, 2013 at 5:00 pm

    #1673121

    Be careful with log drive space when upgrading VCenter. Our adventure last week was a VCenter upgrade that kept growing the VIManage.ldf file until it filled the drive. My solution was to set the Max size of the log file to the drive size -10 GB and temporily add a 2nd Log file to a temporary drive. The total size of both log files eventually reached 130 GB. The correct size for the log file in our VMCenter environment for normal operations seems to be about 30 GB.

Viewing 4 posts - 16 through 18 (of 18 total)

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