locked
SSP Search DB transaction log size repidly growing RRS feed

  • Question

  • Hi All,

    I was being told by the developers and DBA that the SSP Search DB's SQL transaction log was growing very fast (5GB in 15min). To avoid insufficient disk space, the DBA had tried to put in a script that will trigger and purge this transaction log whenever the disk space less than 10GB. However, a SP stored procedure with word "cleanup" stopped the script from purging the log to release disk space.

    There is no others error in the event log except insufficient disk space. My observation, the SSP Search DB size is not growing but its transaction log is growing like crazy. While waiting for the ULS log and DBA to release the disk space so that I can access to the SP central admin, I would like to know what could be the possible root cause and what should I look into.

    Any idea?

    • Moved by Mike Walsh FIN Tuesday, September 6, 2011 5:08 AM admin q (From:SharePoint - General Question and Answers and Discussion (pre-SharePoint 2010))
    Tuesday, September 6, 2011 4:55 AM

Answers

  • Hi JPOlas,

     

    The reasons or scenarios that cause transaction log expansion may be uncommitted transactions, extremely large transactions, operations:DBCC DBREINDEX and CREATE INDEX, while restoring from transaction log backups. You can refer to the following link for more information:
    http://support.microsoft.com/kb/317375

     

    More information: recover from a full transaction log in a SQL Server database:
    http://support.microsoft.com/kb/873235

     

    Thanks,
    Qiao Wei

     

    Thursday, September 8, 2011 11:20 AM
    Moderator