January 6, 2015 at 12:01 pm
Hi all: I plan on upgrading the OS of our SQL server (SQL 2008 R2) from Windows Server 2008 R2 to 2012 R2. Obviously I will be backing it up. We also have a secondary SQL server in reserve in case of a melt-down. Has anyone experienced issues with an OS upgrade like this? Obviously things can go south, but are there common issues I need to to worry about.
After the OS is upgraded we then plan on upgrading the MSSQL application from 2008 R2 to 2012. Any gotchas I need to look out for?
Chris.
January 8, 2015 at 3:01 am
I hope all went well ? The 'day of' is probably not the best time to e asking if there might be any issues 🙂
Generally, in-place upgrades are to be avoided unless you have only one server available. Why not use your standby and move that databases over to that ?
Having said that, I've not seen any major issues with IPU to Windows 2008R2 from Windows 2003, so wouldn't expect much from an IPU to Windows 2012. It's the non-clean install thing I don't like - there may be legacy registry keys and other stuff left over from the original OS....
[font="Courier New"]sqlmunkee[/font]
[font="Courier New"]Bringing joy and happiness via SQL Server since 1998[/font]
January 8, 2015 at 4:03 am
I had done a lot of research but forgot about this forum. The upgrade went fine with just a few minor issues not related to SQL.
So my next step is something I have never done, so I will ask now, way ahead of time. I want to bump SQL from 2008 R2 to 2012. Suggestions?
January 8, 2015 at 4:07 am
Should be fine. You can attach/detach, or backup/restore. Don't forget to rebuild stats and set the db compat level to the latest (or whichever level you need to preserve old behaviours).
Once over to 2012, you can then start to play with columnstore and all the newer stuff 🙂
[font="Courier New"]sqlmunkee[/font]
[font="Courier New"]Bringing joy and happiness via SQL Server since 1998[/font]
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply