棘手的SQL Server在64位机器上安装 - 使用交换！

我的大多数测试服务器仍然是32位机器。直到最近我才开始使用64位机器进行测试。64位平台的主要原因是可以为大型数据库提供更好的性能，因为您可以在这些巨型机器上分配多达2TB的内存。数据库服务器喜欢额外的物理内存。这两个平台上的SQL Server架构本质上是相同的。一个不同之处在于，SQL Server 2008 R2的新特性主数据服务(Master Data Services)仅在64位版本中可用。这就是我开始使用64位的动机。奇怪,但真实。Microsoft Exchange仅在64位平台上可用。Windows Server 2008 R2也是如此。 Surely, SQL Server will follow suit at some point as hardware costs continue to decline. Maybe as early as SQL11 but the initial Denali CTP1 has been released for both 32 and 64-bit. Intel was the first to support Windows with a 64-bit chip named Itanium for the IA64 platform. The trouble with IA64 is there is no true 32-bit backward compatibility so in this case being first to set sail meant nothing as AMD came out with the AMD64 (x64) architecture including the valuable 32-bit compatibility. Intel has since shifted tack to subsequently support the x64 platform through its latest chips but a major iceberg appeared earlier this year when Microsoft stated that it will no longer support the original IA64 platform making the architecture more akin to the Titanic than Itanium. Installing SQL Server 2008 R2 on a 64-bit machine proved more troublesome than expected. Everything goes swimmingly until the end of the setup when it just hangs on the following step: SqlEngineDBStartConfigAction_install_configrc_Cpu64 Optimistically leaving it running overnight does nothing and terminating the setup lets you know that you will need to uninstall before re-installing – setup won’t try taking over where it left off like it used to – I tried that with no luck. The same hanging behavior occurred with both Windows 7 and Windows Server 2008 R2 64-bit editions. Not only that, the same occurred with the Denali CTP1 (aka SQL 11) that was handed out at the PASS Summit. Dang. After searching for a day, I finally found the solution. There is an article on MSDN Blogs on “Windows 7 AppCompat changes and SQL Server client and setup hangs”: http://blogs.msdn.com/b/sql_protocols/archive/2010/08/13/windows-7-appcompat-changes-and-sql-server-client-and-setup-hangs.aspx Yes, it comes down to a simple registry hack to turn on something called “Switchback” that forces Windows to “switch back” to the way it worked before. If only life was this simple. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\AppCompat “To allow SQL Server client drivers to connect, set the SbEnable value to 1 and restart the machine” Well, I followed the instructions and, hey presto, SQL Server 2008 R2 x64 installs completely after the uninstall. Even Denali CTP1 x64 installs too. Thank goodness for Google. OK, I used Bing a little too. In this season of sharing let’s spread the goodwill a little. Cheers Brian