am When you install an "old" SQL Server 2005, I stumbled across a funny detail. I install the SQL Server in the Usually accessible from a base image without service pack and then upgrade the installation by GE downloaded Service Pack. This works perfectly and the installation is in principle "by itself".
When I read the SQL Server 2005, however, wanted to install on a server with 2 Intel 6-core Xeon's broke the installation with a strange error. Unfortunately, I have me the error message no hard copy made, and I'm also the text I already forgot (I'm getting old). Anyway, I was pondering something on what it was. But as I thought made in advance whether a 2005 SQL server with as many cores is clear, I came relatively quickly to the solution:
Before the SQL Server2005 is installed, you should "put down" by the number of cores msconfig for Windows. That means I only have a single core activated, and then ran through the installation perfectly. Then the current ServicePack4 of SQL Server installed, reboot, the cores to msconfig again "released", booted again, and Tata SQL Server detects all nuclei and "everything is good."
0 comments:
Post a Comment