patternsqlModerate
Is there a cool way of performing CU updates for SQL Server on hundreds of machines?
Viewed 0 times
performingsqlhundredswayformachinesservertherecoolupdates
Problem
My company has grown from 50 SQL Servers to over 200 overnight in a merger acquisition. HELP!
My questions are:
-
How can I perform CU updates on this many servers and still have a life and keep my sanity? SCCM doesn't seem to be able to perform CU updates.
-
Has anyone else been able to perform CU updates on 100s of servers?
-
What are some other alternatives?
My questions are:
-
How can I perform CU updates on this many servers and still have a life and keep my sanity? SCCM doesn't seem to be able to perform CU updates.
-
Has anyone else been able to perform CU updates on 100s of servers?
-
What are some other alternatives?
Solution
The
You will need to use the CLI to extract the hotfix, I found that here. Then the CLI options for the SQL Server patch can be found here.
The following commands are what I used to apply the CU6 patch to the local SQL Server 2012 SP2 instance on my laptop. I changed to the directory I downloaded the hotfix to:
You pretty much just work out writing this as a script for each server, then pull in that bit of the summary log (or just the whole log) to a central spot so you can go back and determine the status. Option 2 would be to just include a few lines of code to connect to each instance and verify the build number.
cool way is to use an unattended installation script that simply is called from each server, where the media for the installation is on a central directory on your network, that is accessible from each server. You will have to run the script in an elevated mode, which this is fairly easy in PowerShell.You will need to use the CLI to extract the hotfix, I found that here. Then the CLI options for the SQL Server patch can be found here.
The following commands are what I used to apply the CU6 patch to the local SQL Server 2012 SP2 instance on my laptop. I changed to the directory I downloaded the hotfix to:
.\SQLServer2012-KB3052468-x64.exe /X:E:\Software\SQL_Server\2012\SP2_CU6\Extracted
cd Extracted
.\setup.exe /action=patch /instancename=SQL12 /quiet /IAcceptSQLServerLicenseTermsYou pretty much just work out writing this as a script for each server, then pull in that bit of the summary log (or just the whole log) to a central spot so you can go back and determine the status. Option 2 would be to just include a few lines of code to connect to each instance and verify the build number.
Code Snippets
.\SQLServer2012-KB3052468-x64.exe /X:E:\Software\SQL_Server\2012\SP2_CU6\Extracted
cd Extracted
.\setup.exe /action=patch /instancename=SQL12 /quiet /IAcceptSQLServerLicenseTermsContext
StackExchange Database Administrators Q#105810, answer score: 15
Revisions (0)
No revisions yet.