November 15, 2012 at 1:08 pm
We need to install SQL SP2 and CU1 at multiple sites on SQL/WIN 2008r2 EE clusters with 5 nodes, 22 sql instances, and thousands of databases. The problem is that MS has deployed a non-scalable installer; it runs a Remote Discovery process (RunDiscoveryAction) once for enumeration before installation starts, then again for EVERY sql instance. Each Remote Discovery takes 2.5 minutes, which may not sound too bad until you do the math:
((DiscoveryTime * number of Hosts) * (number of intance +1) ) * Number of Patches = Discovery Time
Our Math is ((2.5*5)*(22+1))*2 = 575 minutes of discovery time.
We've tested this in our lab (Win/SQL 2008r2 EE 4-node cluster with 20 instances) and found the math is correct.
There has to be tons of other shops that have run into this issue. Anyone out there have a solution?
November 15, 2012 at 3:34 pm
how exactly are you installing the updates?
The most efficient way is to run the patch with the AllInstances switch to update in one run.
This article details the switches used
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 15, 2012 at 3:46 pm
That's how we are running it. There is one run of the installer, but every instance kicks off an instance install
"C:\Software\SQL\SQL 2008r2 SP2\"SQLServer2008R2SP2-KB2630458-x64-ENU.exe /qs /IAcceptSQLServerLicenseTerms /Action=Patch /AllInstances
November 17, 2012 at 9:21 am
ah ok, to be honest i've never just sat there and watched it. Incidentally why do you have all 22 instances installed across all 5 nodes?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 18, 2012 at 8:23 pm
DataHammer (11/15/2012)
We need to install SQL SP2 and CU1 at multiple sites on SQL/WIN 2008r2 EE clusters with 5 nodes, 22 sql instances, and thousands of databases. The problem is that MS has deployed a non-scalable installer; it runs a Remote Discovery process (RunDiscoveryAction) once for enumeration before installation starts, then again for EVERY sql instance. Each Remote Discovery takes 2.5 minutes, which may not sound too bad until you do the math:((DiscoveryTime * number of Hosts) * (number of intance +1) ) * Number of Patches = Discovery Time
Our Math is ((2.5*5)*(22+1))*2 = 575 minutes of discovery time.
We've tested this in our lab (Win/SQL 2008r2 EE 4-node cluster with 20 instances) and found the math is correct.
There has to be tons of other shops that have run into this issue. Anyone out there have a solution?
Not really a solution, but you can cut that in half by slipstreaming sp2 and cu1 together into one install.
November 19, 2012 at 7:32 am
Actually that would be a huge help bc it would cut the Remote Discovery events in half. It's what we assumed we were going to do. But it doesn't seem to be possible. This is what we found on the subjet:
Question #1: What is Slipstreaming?
Answer: It is a term used to describe merging original source media with updates in memory and then installing the updated files
Question #10: I already have SQL Server 2008 instance and now I want to update to service pack 1. Do I need to use slipstream?
Answer: No, slipstream will not work when the product is already installed.
November 19, 2012 at 8:51 am
Slipstreaming is performed at install time and can merge an install media with an SP and\or CU on the fly.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 19, 2012 at 9:02 am
My apologies, You're correct that this won't work for your scenario.
You can't combine sp+cu into a patch for sql 2008 (just verified with sp3 + cu6).
It may be supported with R2. I don't have media handy to check.
DataHammer (11/19/2012)
Actually that would be a huge help bc it would cut the Remote Discovery events in half. It's what we assumed we were going to do. But it doesn't seem to be possible. This is what we found on the subjet:Question #1: What is Slipstreaming?
Answer: It is a term used to describe merging original source media with updates in memory and then installing the updated files
Question #10: I already have SQL Server 2008 instance and now I want to update to service pack 1. Do I need to use slipstream?
Answer: No, slipstream will not work when the product is already installed.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply