Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Why do we need to run dbcc updateusage(0) after restoring a SQL Server database on a different server? What are the implications of not running it?

share|improve this question
up vote 2 down vote accepted

You don't need to run dbcc updateusage after you restore a database. The only time that you need to run this DBCC statement is if the output from sp_spaceused isn't being reported correctly or if some of the reports in SSMS (or third party tools) aren't showing the space usage for the database correctly.

share|improve this answer
Thanks...So, after restoring, I will run sp_spaceused in source and destination just to confirm. This will save us a lot of time. Thanks heaps! – Manjot May 22 '12 at 22:14
Even if the number isn't reported correctly this isn't a sign that there is a problem. Depending on your version of SQL Server that you are moving from it may be normal that the number's reported aren't correct as older versions of SQL Server are well known for allowing the space used numbers to drift. This has mostly been fixed in the newer versions of SQL Server. – mrdenny May 23 '12 at 4:56

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.