March 3, 2008 at 2:40 pm
Never worked with 64-bit before, any gotchas I should be aware of as I do an install tomorrow (SQL 2005 Standard). 2 Quad-code 2.5 GHz processors 8 GB RAM.
I'll taken any other 64-bit tips also.
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
March 3, 2008 at 2:48 pm
The only gotcha I would warn about is regarding SSIS packages. When you create an SSIS package with a script task, be sure to select the option to precompile the script else it will fail.
Other than that, we experienced no problems installing DE on either of our x64 systems (both are development).
😎
March 3, 2008 at 2:55 pm
Thanks, Lynn.
See I told you I posted questions.:P
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
March 4, 2008 at 12:55 pm
Okay I am running my install and getting this warning:
- ASP.Net Version Registration Requirement (Warning)
Messages
ASP.Net Version Registration Requirement
32-bit ASP.Net is Registered. Required 64-bit ASP.Net to install Microsoft Reporting Services 2005(64-bit).
I know that the 64 bit version of .NET was installed. I am going to be using SSRS. I have found a fix where you enable 64-bit app pools in IIS by running cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 0. But, being new to 64-bit I am wondering how this will affect development of reports, etc...
Fortunately I am doing this on a Dev server so when I do mess it up, not a big deal, but I would like to only do it once.. This is practice for the production server.
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
March 5, 2008 at 12:48 am
Jack -
The 32 vs. 64 bit IIS/ASP.Net issue is only the first you're going to run into, particularly running SSIS, etc. All of the SQL Server 2005 "core" features are 64-bit but many of the peripheral components (e.g. SSIS), are 32-bit. Some of the bigger challenges include having to install BOTH 32 & 64-bit versions of various drivers (e.g. Oracle) depending on the context in which they'll be used. For example, when accessing Oracle via linked server you need the 64-bit driver as the caller is 64-bit (core database engine) but when using SSIS you'll need the 32-bit drivers. There used to be some pretty substantial differences and different bugs between the 32 & 64-bit Oracle drivers (you do need to download them straight from Oracle, MSDORA does not support versions past 8) but most of those differences have been ironed out in more recent releases from Oracle.
Another thing to remember is that BI studio and the visual studio components also install with both 32 & 64 capabilities and unless you specifically tell the tool that your target environment is 64-bit you may end up with packages, etc. that run 32-bit rather than 64-bit.
Joe
March 5, 2008 at 2:21 am
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.
Also, if you are using DTS, any custom components you put in the windows \System32 folder in 32-bit need to go in the \sysWOW64 folder in 64-bit.
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
March 5, 2008 at 5:50 am
ALIAS
If your using alias' on the server, make sure you create them under both the 32-bit and 64-bit (SQL Native Client Configuration) in the configuration manager.
March 5, 2008 at 8:46 am
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!
March 5, 2008 at 9:05 am
interesting, might explain our challenges in replication we had
one other one is SQLMAIL, it's no more and will not work. in 64 bit only dbmail will work
March 5, 2008 at 9:29 am
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.
Thanks, Ed. I had seen something about 64 bit sql server using the page file.
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
March 5, 2008 at 9:32 am
x86 or x64 SQL Server will use the pagefile after it has reached its maximum available memory regardless. I just don't understand how/why x64 would automatically use the pagefile if not needed ... I've never heard of this.
March 5, 2008 at 9:39 am
Thanks to all for the advice. I managed to get through the install okay. Now for actually using it!
Also I found something interesting about the REporting Services Windows Service account. It still needs to comply with older NT 4.0 restrictions on length. I had my network admin setup specific SQl Server and RS domain accounts and the RS one was long and would not work until we shortened it.
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
March 5, 2008 at 2:37 pm
I am a little late but the problems that I have encountered are:
SSIS compatability problems,
Oracle drivers need to be 64 bit,
openrowset and openrowsource dont work on 64 bit because the MS Jet 4 driver is only 32 bit compatible.
March 6, 2008 at 8:04 am
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.
-- Cory
March 6, 2008 at 8:19 am
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.
Viewing 15 posts - 1 through 15 (of 19 total)
You must be logged in to reply to this topic. Login to reply