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

In the olden days when I used to use other database platforms, we were advised to back up and restore our databases periodically to improve performance.

Common reasons were that a B & R would include

  • rebuild indexes
  • defragment pages

My questions:

What does MS SQLServer do (specifically 2005) when a back and restore is performed?
Should I be doing periodic backups and restores?
Should I be worried about losing statistics?

share|improve this question

You should be doing periodic backups and restores to test your restore procedures, but as far as doing them to improve performance, you can rebuild indexes and shrink files with Maintenance Plans, which is the preferred method.

share|improve this answer

Backups/Restores are carried out at byte level - they have no affect on fragmentation in the database.
Restores should be done regularly to make sure you are confidant in how the process goes (including getting the system attached to the restored database) and that the backups are proved to be usable. Your other answer is correct in saying that index maintenance is a separate process you need to carry out.

share|improve this answer

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.