I have a table on SQL Server 2005 that was about 4gb in size.
(about 17 million records)
I changed one of the fields from datatype char(30) to char(60) (there are in total 25 fields most of which are char(10) so the amount of char space adds up to about 300)
This caused the table to double in size (over 9gb)
I then changed the char(60) to varchar(60) and then ran a function to cut extra whitespace out of the data (so as to reduce the average length of the data in the field to about 15)
This did not reduce the table size. Shrinking the database did not help either.
Short of actually recreating the table structure and copying the data over (that’s 17 million records!) is there a less drastic way of getting the size back down again?
Well it’s clear you’re not getting any space back ! 🙂
When you changed your text fields to CHAR(60), they are all filled up to capacity with spaces. So ALL your fields are now really 60 characters long.
Changing that back to VARCHAR(60) won’t help – the fields are still all 60 chars long….
What you really need to do is run a TRIM function over all your fields to reduce them back to their trimmed length, and then do a database shrinking.
After you’ve done that, you need to REBUILD your clustered index in order to reclaim some of that wasted space. The clustered index is really where your data lives – you can rebuild it like this:
By default, your primary key is your clustered index (unless you’ve specified otherwise).
Marc