March 30, 2017 at 10:56 am
I am migrating from a SQL 2008 server to a SQL 2016 server. This is an important server for reporting, but not production.
Any reason not to backup/restore MSDB from old 2008 server to new 2016 server to bring over all the jobs and packages ??
I also have Reporting Services to bring over, so planning to backup/restore them too.
(It's been a while since I built new servers)
March 30, 2017 at 11:38 am
Packages changed between versions (they are now encrypted). I believe there were other undocumented changes to objects as well. Even without that, there is the complication of the changes in regards to packages.
I see the benefit of the history in msdb, but I generally just script the jobs and recreate them in that type of move. I keep the old server around for historical reference in job history but after a few weeks, it is really not very useful.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply