March 17, 2009 at 9:53 am
Hello all,
I have an SQL 2000 server, I have a DB which is 225GB. We are looking to move this DB over to a different server (SQL 2005) and use vardecimal to hopefully shrink it down a bit.
The problem is that once it has been moved and shrunk down, I can see a massive saving on a per table basis but the DB is still around 225GB in size (even after shrinking).
If I look at the table sizes in excel for all tables on the original SQL2000 DB I can see that added together the DB should be about 400gb in size, yet it is only 225GB. Anyone have any idea how this could be??
Once it has been moved on to the 2005 server I use the same process to add all the table sizes together in excel and it adds up to the correct size (or thereabouts) of 225GB.
Advise please???
Many thanks
Dave
March 17, 2009 at 2:04 pm
On SQL 2000 run DBCC UPDATEUSAGE and check again. There were 'inadequacies' in the way SQL 2000 maintained the space-used metadata in the database.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply