SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Failing SQL 2005 Cluster Installation because of too many cpu's


Failing SQL 2005 Cluster Installation because of too many cpu's

Author
Message
paulrynr
paulrynr
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 5
It is definitely an issue with CPU count not being powers of 2, it was only picked up when the 6-core CPUs started to arrive on the scene and was fixed in higher service packs of SQL 2005 and 2008.
I went to a SQLBits conference here in the UK around Easter and a few of the DBAs presenting mentioned this issue, both with Cluster and Standalone installations.
Setting the CPU count to a factor of 2 will get round the installation issue. Microsoft seem to be a bit reluctant to issue media with the service packs included.
douglasmeakin
douglasmeakin
SSC-Enthusiastic
SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)

Group: General Forum Members
Points: 126 Visits: 167
I also asked our MS Technical Account Mangager at the time for a consolidated release but with no joy.

Officially (I cannot speak of any done internal builds and special customer arrangements) there is no slipstreaming before SQL Server 2008 SP1.

This is due to the architecture that was used before SQL Server 2008 (SP1).
DBADave
DBADave
Ten Centuries
Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)

Group: General Forum Members
Points: 1355 Visits: 1109
We encountered the same problem in April. I got lucky and found one discussion regarding the issue, which pointed me to the KB article.

http://relatedterms.com/ViewThread.aspx?t=1464269

We also tried reinstalling the OS prior to finding the fix. Now whenever we encounter any strange problem with our 24 proc servers we start wondering if it's related to the proc bug/feature.

Good article. Hope it saves people some time when they encounter the problem.

Dave



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search