SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a heavy used site collection with a 30GB quota limit on the content DB - WSS_WebApp_Content1, I have verified the 'dbo.AuditData' table and found that it has 1.4c records and is 35 GB in size.

Why SharePoint is not considering 'dbo.AuditData' table while calculating the site-collection size? and what are all the other tables treated like this ?

share|improve this question
I am also looking for an answer to the same question. – Anonymous Aug 23 '10 at 8:29
up vote 1 down vote accepted

A site collection quota is set to manage content in a site collection. There are tables in the database that store things other than content. The Audit Data is one example of that, in addition there are some user information tables.

share|improve this answer
As the 'dbo.AuditData' table occupies more than 35GB, we are facing some SQL issues. can we set a quota kind of setting against this table to restrict the auto growth & would be the your suggestion for me now? – Karthikeyan Jun 10 '10 at 17:39
You can do normal DBA things in SQL Server to adjust the autogrowth properties. You can also look at adjusting the audit settings in SharePoint so that less data is retained. – Mike Oryszak Jun 10 '10 at 21:28
If we enable audit for all possible events, does the stored procedure 'proc_AddAuditEntry' be executed at the moment when user perform any action? I know, the answer is 'Yes', still would like to confirm. we are facing DB deadlock issue due 'proc_AddAuditEntry', do you have any suggestion for me. – Karthikeyan Jun 12 '10 at 0:48
I would strongly suggest Mike's suggestion of looking at the audit settings to see what's retained. If you have Auditing enabled your business will have that as a requirement, and they must state what is to be retained and for how long. Once that requirement is set in stone, your Database requirement becomes a prerequisite for that to happen. If you run out of storage, that requirement should be enough of a reason to buy more storage. Out of curiosity, how many users are accessing the site at the same time, in order for the deadlocks to occur? – James Love Aug 23 '10 at 9:30

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.