Sharepoint Config DB size grown to 25 GB
My sharepoint farms' config DB size has grown to 25 GB leaving no sapce on disc. That to alone Config_log.ldf file is of 24.5 GB.how can i truncate size of this log DB?Is there any way to limit the size of Sharepoint Config DB?Thanks in advance.
March 26th, 2008 7:34am
Truncate Config DB as a regular SQL transaction log file truncation. it has nothing to do with sharepoint programming forum. however here is how i truncate the log, run these in Query window in SQL USEDatabaseNameGODBCCSHRINKFILE(<TransactionLogName>,1)BACKUPLOG<DatabaseName>WITHTRUNCATE_ONLYDBCCSHRINKFILE(<TransactionLogName>,1) transaction log name is your config database ldf file name without .ldf extension. database name is your wss config database name.
April 21st, 2008 10:41pm
Thank you for the response. My apology for putting misleading question. Actually truncating is not an issue but as my sharepoint config DB is growing to 25 GB in 2-3 days after each time I truncate the DB.And I am not able to figure outhow this is happening as I am not doing any major updation on mysharepoint portal.So my problem is how I can set restrictions on Config DB so that it will not grow beyond a limit. Thanks a lot.
April 22nd, 2008 8:02am
Moving to the admin forum
April 22nd, 2008 7:35pm
This is happening because all the databases (Except for the search and ssp databases) are set to full recovery mode by default. Full recovery mode does not auto shrink / truncate the log files on a full backup. You can change this to simple recovery mode and it will auto truncate on full backups. Microsoft does not recommend changing to simple recovery mode in a production environment. Full recovery mode allows the SQL admins to backup the transcation logs incrementally, simple recovery mode does not allow this and only allows full or differential backups, no transaction log backups. I assume you need full recovery mode to do log shipping and mirroring as well.
April 24th, 2008 3:53am
Hi, My config database (sql 2005) is on full recovery mode. The transaction log grew too big about 34GB. So, what I did was 1. Shrink file using dbcc shrink file 2. Backed up the transaction log to a file 3. Shrink file using DBCC shrink file again Now here is my question, I know if I use the truncate only option on step2 and shrink the file, it will reduce the log file size. But If I do this I am seeing messages on event viewer saying "BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log." Since, I have backed up the log file in step2 to a file, Can I safely truncate the log file? If so Will I be able to recover to a point in time?
August 24th, 2009 11:43pm
I don't know squat about sql, but our guy who does just informed me that ours has grown to 150GB. I think i have stumbled upon a source for wild ldf log file growth: a sharepoint workflow which automatically triggers on file modification, which in turn modifies the file. I'm turning it off and we'll see if our seriously rapid growth stops.
February 1st, 2011 6:14pm