64-Bit Install Gotchas

Question

64-Bit Install Gotchas

Viewing 5 posts - 16 through 19 (of 19 total)

You must be logged in to reply to this topic. Login to reply

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 1

Adam Bean (3/6/2008)
Cory Ellingson (3/6/2008)
The biggest issue I had was with linked servers from the 64bit to 32 bit SQL servers. I had to run an update on all the 32 bit linked servers, instacat.sql I believe.
That should only be for 2005 to 2000 connections. x64 to x86 2005 should not need this.

I do believe you are correct on that. That is what we needed to do to access our x32 SQL Server 2000 systems. The x32 SQL Server 2005 servers were fine.

😎

Jack Corbett SSC Guru Points: 184394 More actions · Answer 2

Adam Bean (3/6/2008)
Cory Ellingson (3/6/2008)
The biggest issue I had was with linked servers from the 64bit to 32 bit SQL servers. I had to run an update on all the 32 bit linked servers, instacat.sql I believe.
That should only be for 2005 to 2000 connections. x64 to x86 2005 should not need this.

My current situation is just beginning to migrate from Foxpro to SQL Server and C# so all we really have is this new install of 64 bit SQL Server. There is a SQL Server 2000 personal edition running in our accounting office (long story), but the plan is to upgrade that application as well including migrating the database SQL05 Server. Partially because there were no backups being done on the other system and no one was managing it prior to a crash, which is when I became aware of the system.

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

Adam Bean One Orange Chip Points: 26631 More actions · Answer 3

Adam Bean (3/5/2008)
EdVassie (3/5/2008)
Hopefully you will haveseen this already, but in 64-bit you MUST set the upper memory limit for SQL Server. Otherwise it treats the pagefile space as part of the server memory and you end up with some of SQL memory permanently on disk.
Ed, this has me intrigued as I've never heard of this until now ... Regardless, I've always set my min and max on a production environment, but this is definitely good to know if it's true.
Do you have any links explaining this?
Thanks!

Can anyone shed some light on this? I'm really curious as I've always heard differently (even from M$).

EdVassie SSC Guru Points: 60472 More actions · Answer 4

Here are some references about setting a maximum memory limit on SQL Server 2005

http://blogs.msdn.com/sqlprogrammability/archive/2007/04/30/will-64-bit-increase-the-performance-of-my-sql-server-application.aspx

http://support.microsoft.com/kb/918483

Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

Carl Rimmer SSCarpal Tunnel Points: 4068 More actions · Answer 5

Another Gotcha I found was if you develop an SSIS package on a 32 bit machine and deploy on a 64 bit server it fails when running via the GUI for running SSIS packages. The workaround was to run the package via the dtexec command line utility in the 64bit directory.