Enterprise edition on x64bit standard 2003 server

[loriek]

SQL 2005 Enterprise edition will run on x64 bit standard 2003 server, but what are the drawbacks?

Thanks.

 

[fuzzyocelot]

The drawbacks (or challenges) we've run into with running the 64-bit version of SQL Server 2005 are mainly with Reporting Services and Integration Services. When you install the 64-bit versions, Reporting Services is 100% 64-bit compliant. I found out that means you can't use 32-bit drivers for the data. You must use 64-bit drivers.

We have 50+ SQL 2000 DTS packages that we need to eventually convert to Integration Services packages. We just don't have the time right now. So we've had mixed luck in getting the packages to run under SQL 2005 64-bit. In BOL, look up "Integration Services Considerations on 64-bit Computers". That will show you the limitations with SSIS on 64-bit computers. We've run into those issues and have worked around them for now. We're still testing on our 64-bit development server.

From our experience, we haven't run into a lot of problems running the 64-bit version. Just some challenges such as using Oracle drivers, but that's a long story. Basically we've had problems with the Oracle 64-bit drivers and last I heard Microsoft doesn't plan on developing an Oracle 64-bit driver. So we've had to use the 32-bit version which runs under a different ODBC Data Source Administrator.

Also keep in mind that anything that's 32-bit runs under WOW (windows on windows) mode and by default is installed under a different directory (i.e. Program Files (x86)). The parentheses can cause problems with some applications. So you can try to install those applications under a different folder that doesn't have the parentheses.

I hope this helps. Anyone please correct me if I'm wrong on anything.

 

[loriek]

Sorry, what I meant to ask are what are the drawbacks of running on Standard edition server instead of Enterprise edition if you're running Enterprise 2005.

Thanks.