June 14, 2017 at 9:35 am
I was reading this article here on SSC about SQL Server Migrations and i didn't go too far before this concern popped in my head because migrating the Master and MSDB system databases in a migration procedure is not something that is practiced in my environment whether in the case of a like to like version migration as in the case of that article, or in the case of an upgrade. The writer did mention that is was their decision to follow this procedure but didn't talk about the "why" of it all.
So my question for this professional family is; when or why would it be necessary that Master or MSDB should be considered in a migration?
Possibly because there might exist some custom code that needs to be migrated too?
What else can you think of?
Thanks in advance for your thoughts and contributions!
June 14, 2017 at 10:20 am
Logins, jobs, linked servers, certificates/cryptographic instruments
Anything that is stored in master/msdb and used for your system might need to be migrated. Can be scripted in most cases.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply