|
|
Posted by Erland Sommarskog on 12/29/07 23:29
Neil (nospam@nospam.net) writes:
> OK, I looked at the data a bit that has been changed. The database backup
> the night of 12/20 was 1.2 GB. The database backup the night of 12/21 was
> 3.3 GB. So whatever happened had to have happened on 12/21.
>
> Nevertheless, looking at ALL changes from 12/21 through the current
> database, roughly a week's worth of changes -- all records that have
> been added or modified in that table since 12/21, the entire amount data
> in all of those records is about 1.5 MB -- about 1,000 times short of
> what it needs to be.
>
> So there's no way that data added or modified caused this change. For some
> reason this table went from 1/2 GB to 2 GB overnight, with hardly any
> changes to the data. This is just very strange.
And
SELECT SUM(datalength(textcol1)) + SUM(datalength(textcol2)) + ...
FROM Description_Docs
returns what?
I don't know if you can get fragmentation in text columns, but I guess
you can. But it would hardly happen out of the blue. Unless, hum, you
passed some magic threshold? Nah...
Anyway, you could try running DBCC CHECKTABLE on the table, or DBCC CHECKDB
on the database to see if there is any corruption.
You could also test the effects of DBCC CLEANTABLE.
Yet an idea is to copy the table to another database, and see how
much size it takes up there.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|