Skip to main content

Reclaim Unused Table Space ...

If we ever remove a variable length column (varchar) or TEXT column from one of our table, a certain amount of wasted space will be there in that table's physical representation. We can reclaim this space with the DBCC CLEANTABLE statement. Let us see how to use DBCC CLEANTABLE with a sample code snippet

Sample table structure

CREATE TABLE TableWithText
(
[FirstName] [char] (50),
[Age] [int] NULL,
[Resume] [text]
)
GO

Insert sample data into the table.

Insert into TableWithText Values ('Vadivel',28,'AAAAAAAAAAAA')
Insert into TableWithText Values ('Sailakshmi',27,'BBBBBBBBBBB')
Insert into TableWithText Values ('Vadi',58,'CCCCCCCCCCCCCCC')

To check the size of the table

sp_MStablespace TableWithText

Now let us drop the column ("Resume") with Text datatype

Alter table TableWithText drop column Resume

Try to check the size of the table again

sp_MStablespace TableWithText

There wouldn't be any change in the size of the table. Actually as we have removed a column of TEXT datatype we need to expect the size of the table to reduce down considerably. For that execute the below sql statement

DBCC CLEANTABLE ('pubs','TableWithText') -- parameters are database name and the table name

Drop the fixed length ("FirstName") column now

Alter table TableWithText Drop Column FirstName

Now if you check the size of the table there won't be any change at all. Thats because we reclaim the space only if we remove TEXT or variable length fields from our table.

DBCC Cleantable has an optional third parameter where we can specify the batch size. i.e., the number of rows which would be processed per transaction. If not specified, the statement processes the entire table in one transaction this might sometime throw timeout error.

DBCC CLEANTABLE ('pubs','TableWithText', 2)

Related Links:

1. Reclaiming a table space after dropping a column [With Clustered Index] - http://vadivel.blogspot.com/2007/10/reclaiming-table-space-after-dropping.html

2. Reclaiming the table space after dropping a column [Without Clustered Index] - http://vadivel.blogspot.com/2007/10/reclaiming-table-space-after-dropping_01.html

Comments

Anonymous said…
Just in case somebody, like myself, will stumble upon this post trying to find how do you reclaim space after dropping a fixed size column here it goes.
If there's a clustered index on the table you can use DBCC DBREINDEX on it. If not, then a clustered index can be created and then dropped - it also should do the trick as both of these methods trigger table rebuild. Unfortunately both only work in SQL2005+. If you have an SQL2000 you'll have to recreate the table manually.
Vadivel said…
Alexander, I have written couple of posts discussing about those in detail. I have now linked them under 'Related Links' section within this post. Check that out.

Popular posts from this blog

Script table as - ALTER TO is greyed out - SQL SERVER

One of my office colleague recently asked me why we are not able to generate ALTER Table script from SSMS. If we right click on the table and choose "Script Table As"  ALTER To option would be disabled or Greyed out. Is it a bug? No it isn't a bug. ALTER To is there to be used for generating modified script of Stored Procedure, Functions, Views, Triggers etc., and NOT for Tables. For generating ALTER Table script there is an work around. Right click on the table, choose "Modify" and enter into the design mode. Make what ever changes you want to make and WITHOUT saving it right click anywhere on the top half of the window (above Column properties) and choose "Generate Change Script". Please be advised that SQL Server would drop actually create a new table with modifications, move the data from the old table into it and then drop the old table. Sounds simple but assume you have a very large table for which you want to do this! Then it woul

AWS fatal error: An error occurred (400) when calling the HeadObject operation: Bad Request

While using AWS and trying to copy a file from a S3 bucket to my EC2 instance ended up with this error message. Command Used: aws s3 cp s3://mybucketname/myfilename.html /var/www/html/ Error: fatal error: An error occurred (400) when calling the HeadObject operation: Bad Request The error goes off if we add the region information to the command statement. I am using Asia Pacific (Mumbai) so used ap-south-1 as the region name. Modified Command: aws s3 cp s3://mybucketname/myfilename.html /var/www/html/ --region ap-south-1

[Non Tech] Want to know the recipe for Omelette :)

Fed up with Bread - Jam and Curd Rice, today i wanted to eat Omelette. Interesting part is I wanted to cook it myself :) So in the first picture you see all the items which are needed for preparing an Omelette. When I had a closer look at the eggs I see that almost all the eggs are broken. But believe me when I bought it couple of days back it was in perfect condition! I was wondering whether the eggs have become rotten or pretty old to consume! I tried taking an egg and break it but couldn't break it at all :) Since I have kept in the freezer all the eggs have frozen and looked like a iron ball :) After trying for few minutes of trying i removed the shell of the egg and then kept that iron ball :) into a bowl and placed it within Oven. I heated it for 1 minute and checked. It melted only to a limit. So i just set it for another 2 minutes and checked it later. It has melted but the part of the egg white has become a Omelette :( I didn't leave it there. I took the bowl out of