MSSQL1/MSSQL2 upgrades tonight, MSSQL3 tomorrow night

Stephen

Stephen

US Operations
Staff member
We will be upgrading SQL services on MSSQL1/2 tonight between the hour of 8pm and 8am tomorrow. We are going to be doing a complete upgrade of OS, and of SQL Server versions. To ensure data reliability we will be stopping the SQL services to complete the upgrades, which will mean they may be inaccessible for between 2-6 hours timeframe. We will also be keeping a close eye on all logs to see if any errors in the process, and get them resolved ASAP if they are seen upon the first DB connection to the new servers.

These upgrades are being done to modernize and upgrade the network and servers.
 
MSSQL1 DBs are coming back online, we're having a few more complications with logins than expected, and will not be doing MSSQL2 at the planned time this period, but instead later tonight.
 
MSSQL2 upgrade is happening in just a short time now and will be unavailable for connections, and then we will see the upgrade process through. Backups are completing at this time.
 
MSSQL2 upgrades have mostly happened, we're working on clearing up any errors or remaining problems throughout the day as we see errors in the logs.
 
The MSSQL3 move will be done Saturday night. While the schedule has been a little more fluid than I'd like with moving these, we're trying to make it as painless as possible. There have been a handful of databases with schema issues in upgrade and some other faults found making sites not load right and we've been addressing them and fixing.
 
Last edited:
We've run into some unexpected complications in the update and move to new SQL version here today, and will be having to make an extra step thats going to take several extra hours to resolve.
 
Forgot to provide a further update as we've been quite busy. The most used SQL DBs are all upgraded and live, there may be some stragglers we are still working on but if a website tries to access we get an error notice and start to bring it online within minutes.
 
We have found an issue that the CL2-WIN10 server was having an issue communicating to the new server, it is now resolved. Thank you for the reports, we are able to trace the issue down to a routing matter between subnets.
 
You must log in or register to reply here.
Back
Top