June 10, 2015 at 2:32 am
Morning / Afternoon/ Evening.
I have a general question about SQL patching and your processes that you have in place.
I was wondering what you do in your shop? Do you have a patch policy in place with your version of SQL? (whatever that maybe) Do you methodically work to a service pack level or do you patch your SQL Servers based on whenever / CU / security updates are released?
June 10, 2015 at 3:37 am
Usually follow the Cumulative Update path. When they come out, get them, put them on Dev, see what happens there and then slowly march them through the various environments prior to releasing to production. Waiting for SPs these days is a waste of time. Microsoft is releasing fewer and fewer of them on a slower schedule.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 10, 2015 at 7:27 am
We generally stick to SPs. Way too onerous and too many outages to keep up with CUs.
for a new system from scratch could start with the latest (or near latest) CU, as it can be started in dev and fully tested then rolled through the environments.
I would always steer clear of applying the latest CU immediately. The first 5 CUs after SQL2012 SP2 are a case in point, CUs 4 and 5 caused issues with a fix in CU1 that addresses online reindexing corrupting data.
---------------------------------------------------------------------
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply