Good to hear. There are all sorts of views that connect the application database to the system database and doing a restore like you did can leave those view pointing to the wrong place. Whenever you do this you should always go to database maintenance and rebuild the views or you will have issues. I am guessing, by what you said, that, in order to test the upgrade prior to putting it in the production environment, you made a copy of the production database, restored it in a different location even possibly a different SQL server instance, did your testing, made a backup and then restored that over the production database as opposed to running the full database update against the production database. All this, to save what entries you made in the test environment. While such a line of thought sounds reasonable, you really do need to run the full database update process against this test database after it is restored over the production database.
↧