I have a couple of SQL 2008 R2 servers running on Win 2012 that need to be upgraded. One to SQL 2014 and SQL 2016, I want both on Win 2016 for application compatibility. I don't want to do an in-place upgrade, but the applications that talk to these server are very cumbersome to relocate SQL. These servers have already been through at least one in-place OS upgrade and maybe one in-place SQL upgrade so I would really like to do this cleanly. back in the 2005-2008 days, I did a Side/Side upgrade where I built an identically configured SQl server using the same Instance names/folder paths, took the old server offline, copied the DB's over, master and all, renamed the new server to the old server name, started everything up. The last step was to check that the server name was correct in the master DB.
Will this strategy still work ok in modern SQL? Is there anything that gets left behind doing this for and SQL construct, ie. jobs, linked servers, etc (understanding I have to deal with any report servers etc)?
Thanks