You can run DBCC SHOWCONTIG on both tables, and compare the results looking
MCSE, SQL Server MCT, MVP
> The table size was unreal like one table was showing 397,756 KB. When I
> created another table with the same specs and transferred the data over,
> new table showed 6,152 KB.
> The original table showed the same 397,756 KB with sp_spaceused, and dbcc
> updateusage did not change it any.
> Any reason why this table could appear so bloated? Any suggestions how
> >> We have several tables which show unreal table sizes (much too big)
> >> viewed in the Manage Index screen (ver 6.5).
> >What calculation do you compare/base that conclusion on?
> >> Aside from transferring the data into another table and dropping the
> >> original table, is there an easier way to rectify this situation?
> >Will DBCC UPDATEUSAGE help (recalculate in the index dialog) help?
> >You could trace E.M. and see that it calls sp_MSindexspace. Since it's
> >sp_you'll find the source in E.M.....
> >MCSE, MCSD, MCT, SQL Server MVP
> >Cornerstone Sweden AB