I have a few databases that are much larger on the SQL server then is shown via stsadm or in Central Admin. I can figure out what is making it so much different, we are talking about 30 GB or a 33% difference. A few were resolved by trimauditlog parameter but the rest I cant seem to figure out.

Hi, The content DB size also includes versions as well. This also includes user analytic reports. I hope this will help you outThanks, Rahul Rashu

So they enumsites size and the quota dont include versioning?

Did you check how much data is in the recycle bin ? Also the Content DB size is always much larger than the size of actual content uploaded on the site. Its the way the site is constructed. We had some 30 GB documents uploaded to our site and the content DB blew up to 70GB. It also depends on the type of files you are uploading. If you are uploding htm/html files it scans them for href tags, that was what happened in our case.-Pushkar

Seems like the largest table is the AllUserData table. I am looking for reasons it happens and how to solve if possible. In what numbers is the recycle bin counted? I think its counted in quota via Central Admin but not via stsadm(enumsites), is that correct? In your example what would cause such a differecne of more then double? If it can be double is that normal expect behavior? thanks

no they wont.Thanks, Rahul Rashu

Hi, The content DB size also includes versions as well. This also includes user analytic reports. I hope this will help you outThanks, Rahul Rashu