Once you bring the instance back up you will need to re-patch back to your original level. One way around this is to create your new instance, shut it down, and copy the master.mdf, mastlog.ldf, MSDBData.mdf and MSDBLog.ldf files to the locations they exist for the instance (copy/rename the originals first of course). Here is some light reading on the subject for you.īack Up and Restore of System Databases (SQL Server)Īlso I should point out that you can only restore master and possible msdb on an instance that is the exact same build number. If you've never made any changes to it you can probably skip it, but it doesn't hurt to bring it along also. master primarily will be your logins and list of databases. In Object Explorer, connect to an instance of Database Engine. In fact msdb will contain all of your jobs and any ssis packages that you have stored in the instance. To restore the master database, you need the SQL Server instance in the single-user mode. Using Transact-SQL To restore the service master key Retrieve a copy of the backed-up service master key, either from a physical backup medium or a directory on the local file system. If you want to move the entire instance you can backup and restore the system databases, but make sure you get more than just master. You can refer to my script at ( make sure you do a backup restore and not detach/attach method - now learned it !!).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |