Those items at the database level should all live inside of a user database. You also asked about indexes, stored procedures, views. I find that playing with system database migrations and upgrades through restore to sometimes cause frustrations with the restores and it can carry over potential sins. I am not a fan of restoring system databases when doing an upgrade migration and I prefer doing migrations over in place upgrades as I discussed in this lengthy answer to another question.īasically I like to start "fresh" when I do a migration. Select a consistency check to be run after the restore.Īfter the restore, SQL restarts in multi-user mode.Max gave a decent answer which I will upvote once I'm done typing this alternate view up.
To ensure that Backup Exec has access rights, verify that the account that Backup Exec uses has administrator rights to the computer that is running SQL. If Backup Exec does not have access to the SQL registry keys HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server and HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer, then a restore to the default directory may not work, and the option Automate master database restore on the restore job properties for SQL will not work. When this option is selected, only the master database can be restored if this option is selected for any other database, those jobs will fail. On the Restore Job Properties for SQL dialog box, select Automate master database restore.Īll existing users are logged off, and SQL Server is put into single-user mode. On the Properties pane, under Settings, click Microsoft SQL. On the restore selections list, select the backup set containing the last master database backup.
On the Properties pane, under Source, click Selections. On the navigation bar, click the arrow next to Restore.
0 kommentar(er)
