December 12, 2011 at 4:48 am
Hello,
We are planning on doing an in-place upgrade on our SQL Servers OS. They are either 2008 R2 of 2005 R2. The OS is Windows server 2008 R2 64 bit Standard, we are actually upgrading to Server 2008 R2 Enterprise. I was just wondering (apart from a full back up) if anyone had any tips for this? I will be stopping and disabling the SQL services during the upgrade, the machine name etc will still be the same. I feel as though it isnt too much to worry about as the OS isnt really changing. We are dong this to get over the memory restriction of Windows 2008 R2 standard, which is 32GB.
Any hints or tips are appreciated, thanks for reading.
Regards,
D.
December 19, 2011 at 7:14 am
I have not done this type of license upgrade, but what you said looks reasonable: take backups, shut down SQL, apply OS license change, reboot, start up as normal.
I would definitely test this process before applying it to a production server. If I did not already have a suitable test environment built then I would build one.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
December 19, 2011 at 8:38 am
run the Micrsoft toolSQL Server 2008 Upgrade Advisor than you will get very good idea.
December 19, 2011 at 8:43 am
Microsoft Upgrade Advisor article
http://www.mssqltips.com/sqlservertip/2184/overview-of-microsoft-sql-server-2008-upgrade-advisor/
December 19, 2011 at 8:54 am
The upgrade advisor isn't applicable for an OS upgrade, only a SQL one.
There shouldn't be any issues with your OS upgrade, but take backups, move them off the machine, just in case. Or even think about a P->V conversion for the existing system as a backup. Worst case, you have the VM image to reference if you end up reinstalling things.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply