|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Sunday, August 09, 2009 7:51 AM
Points: 1,
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.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Tuesday, April 24, 2012 2:25 AM
Points: 120,
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).
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: 2 days ago @ 9:22 AM
Points: 454,
Visits: 789
|
|
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
|
|
|
|