Btw, one of the columns of XML type if it helps you.

It's when you don't like good news :crazy:

CHECKDB found 0 allocation errors and 0 consistency errors in database 'MyDatabase'.

Yes but not on stage where I currently do testing.

CirquedeSQLeil (9/27/2010)

---

There used to be...

Will do a little later after running DBCC...

Hmm... even TRUNCATE didn't work! Any suggestions before I re-created the table?

ALTER TABLE tablename REBUILD did not change any table size returned by sp_spaceused

miksh (9/27/2010)

---

unused[/b] space which is based on sp_spaceused 1864 KB while reserved space...

Derrick Smith (9/27/2010)

---

Run this and see if there's an index using more space than the others (significantly, anyway). Replace the tablename_here with your table name

select

'['+DB_NAME(database_id)+'].['+c.name+'].['+d.name+']' as [DB.Table]

,b.name as [Index...

getoffmyfoot (9/27/2010)

---

Yea, the drop/create table is brutal... however what about drop/creating all the indexes if they won't shrink? if the table has 0 rows that seems like a pretty safe...

Well, it didn't help.

Yes we did. Recently we kept data allocating ~1.5GB and now decided to...

Hmm.... very brutal solution. Anything else possible for SQL 2005?

Btw, Shrink Dtabase/File Task dialog in Mgmt Studio shows that the only 3GB could be freed but that table has 8GB...