When I run sp_spaceused 'table', @.updateusage = 'TRUE', here is what I get:
name rows reserved data index_size unused
-- -- -- -- -- --
table 0 7253 KB 5020 KB 32 KB 2201 KB
How come that empty table still occupies lots of space?It seems that in some moment before such table contained rows (and had an
index).
Try a DBCC UPDATEUSAGE on the whole database or DBCC CHECKTABLE on the
interested table
"Leon Shargorodsky" wrote:
> When I run sp_spaceused 'table', @.updateusage = 'TRUE', here is what I get:
> name rows reserved data index_size unused
> -- -- -- -- -- --
> table 0 7253 KB 5020 KB 32 KB 2201 KB
> How come that empty table still occupies lots of space?
Monday, March 12, 2012
Inconsistent sp_spaceused
Labels:
database,
inconsistent,
index_size,
microsoft,
mysql,
oracle,
reserved,
rows,
run,
server,
sp_spaceused,
sql,
unused,
updateusage
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment