Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. 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

If I take a backup of a database on a SQL 2005 Server, and then restore that backup to a different (new) database on the same database server instance, what things will not be persisted (things like cached execution plans, statistics etc...)

share|improve this question

migrated from Jan 21 '12 at 16:48

This question came from our site for professional and enthusiast programmers.

up vote 5 down vote accepted

Plans will be recreated at first run.

Otherwise, everything database level will be there except where it interacts at the instance level, such as:

  • replication
  • backup jobs/schedules
  • maintenance plans/schedules
  • login mappings to users

For a standard, everyday database, you've no worries.

share|improve this answer
also any custom stored procs that have been added to the "master" database – Ian Ringrose Jun 17 '09 at 16:53
good point, I'd say this "instance level" though – gbn Jun 17 '09 at 16:55
+1, you're over 8k now... – KM. Jun 17 '09 at 21:23

Orphaned Users are often the result of restoring MS SQL Server databases. Here's an article on fixing orphaned users.

share|improve this answer

I am not sure if I have been doing it incorrectly or not, however, when I do a restore it never seems to carry over user information. I end up needed to re add them manually (or through another script).

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.