<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
SQL Server 2008 High Availability
»
SQL SP/CU taking HOURS on Multi-Node...
SQL SP/CU taking HOURS on Multi-Node Multi-Instance Cluster
Rate Topic
Display Mode
Topic Options
Author
Message
DataHammer
DataHammer
Posted Thursday, November 15, 2012 1:08 PM
Forum Newbie
Group: General Forum Members
Last Login: Monday, February 11, 2013 7:46 AM
Points: 9,
Visits: 173
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?
Post #1385331
Perry Whittle
Perry Whittle
Posted Thursday, November 15, 2012 3:34 PM
SSCertifiable
Group: General Forum Members
Last Login: Yesterday @ 5:53 AM
Points: 5,204,
Visits: 11,158
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"
Post #1385381
DataHammer
DataHammer
Posted Thursday, November 15, 2012 3:46 PM
Forum Newbie
Group: General Forum Members
Last Login: Monday, February 11, 2013 7:46 AM
Points: 9,
Visits: 173
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
Post #1385386
Perry Whittle
Perry Whittle
Posted Saturday, November 17, 2012 9:21 AM
SSCertifiable
Group: General Forum Members
Last Login: Yesterday @ 5:53 AM
Points: 5,204,
Visits: 11,158
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"
Post #1385946
SpringTownDBA
SpringTownDBA
Posted Sunday, November 18, 2012 8:23 PM
Old Hand
Group: General Forum Members
Last Login: Yesterday @ 9:19 AM
Points: 316,
Visits: 1,484
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.
Post #1386135
DataHammer
DataHammer
Posted Monday, November 19, 2012 7:32 AM
Forum Newbie
Group: General Forum Members
Last Login: Monday, February 11, 2013 7:46 AM
Points: 9,
Visits: 173
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:
http://blogs.msdn.com/b/petersad/archive/2009/04/24/sql-server-2008-slipstream-frequently-asked-questions.aspx
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.
Post #1386399
Perry Whittle
Perry Whittle
Posted Monday, November 19, 2012 8:51 AM
SSCertifiable
Group: General Forum Members
Last Login: Yesterday @ 5:53 AM
Points: 5,204,
Visits: 11,158
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"
Post #1386442
SpringTownDBA
SpringTownDBA
Posted Monday, November 19, 2012 9:02 AM
Old Hand
Group: General Forum Members
Last Login: Yesterday @ 9:19 AM
Points: 316,
Visits: 1,484
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:
http://blogs.msdn.com/b/petersad/archive/2009/04/24/sql-server-2008-slipstream-frequently-asked-questions.aspx
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.
Post #1386444
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
