Starting last Thursday a content db we are using on one of our site collections started to grow very rapidly. It was increasing in size by 256MB at a time. From midnight 1am until about noon yesterday it went up by 13GB and the log is increasing dramatically as well. From 4:31am until 4:33 there were 13 hits and the size increased by 3.25GB, 256MB at a time. I am running a little util I created that logs any changes to libraries and lists from a specific date or time. The scan is about 1/2 done. I can see lots of updates and additions, just nothing that could account for such a large increase so quickly. Anyone have any idea what could be causing this?

Hi Greg Shell, First, check if Audit is enabled. Enabling Auditing will consume lot of space on your SQL server. You may find the differential data occupied by the Audit Data. If so, please refer to the following blog to fix the issue: Why a content database grows abnormally? http://blogs.technet.com/b/damodar/archive/2009/03/12/why-a-content-database-grows-abnormally.aspx If you don’t enable audit, please check the SQL server configuration: 1. Right click on the concerned database, click on Tasks, click on Backup. This should truncate the LDF file. 2. If this does not work, change the recovery model to Simple. 3. If this too does not fix the issue, change the Autogrowth option. For more information about "autogrow" and "autoshrink" in SQL server, please refer to the following article: Considerations for the "autogrow" and "autoshrink" settings in SQL Server http://support.microsoft.com/kb/315512 Regards, Rock Wang Microsoft Online Community Support

Thanks for the repsonse. The problem was a couple workflows in a loop with records that had big attachments. What a mess. I was not sure what to do at first except review the db transaction logs to get a better idea about what was going on. Instead I wrote a little app to check for high activity by getting the version count for all list items and library documents. This site collection has about 1900 sites but I got lucky and started looking in the write branch of the collection. It could have taken a day or two to look through every list and library in every site. But after the app had run for a few hours I noticed the log it was keeping had recorded a list item with about 9500 versions. It had been running the count on the next list item for quite a while so I opened the list and the record showed about 38K versions, 35K for another, 33 for another and 28 or so for another. I deleted the records, stopped the workflow and then opened the recycle bin. Those 5 records totaled about 190GB. I contacted the author and fixed the workflows. I wrote a little app that saved a list of all the workflows and then runs once a day to report any new or udpated workflows. They can now be reviewed and I know who is doing what with all the workflows.