December 18, 2020 at 9:56 am
Just trying to get an idea of what steps folks are doing to make sure their updates are safe and work. For instance are you building a dev server to test on? Do you push all of your jobs to that server as well to test the update?
Also have you ever had a cu or so update fail to update or one that caused problems? What did you do?
December 18, 2020 at 4:37 pm
always start in lower environments (Dev, Test, Stage, Prod) or something similar. The Environments should be relatively the same. There may be different code in different environments depending on where it's been deployed. Haven't run into any issues with CU or update failing.
For better, quicker answers, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 18, 2020 at 5:55 pm
Before applying a CU or SP in *any* environment - make sure you have good backups of all databases. If you ever do run into an issue with a patch and have to rebuild the system you want to be able to restore with minimal data loss (no data less is preferable - of course).
If your system is a VM - you may be able to take a VM snapshot of the server before applying the CU, but you still want SQL backups available.
For production environments it gets trickier...which is why I want my production systems setup in cluster. Either a failover cluster or AG - where we can perform the upgrade on the non-active node and then failover. If the CU fails on the non-active node for any reason we just do not fail over to that node.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply