SQL Server 2005 64bit ODBC Connection

roy · Post by **roy** » Mon Mar 26, 2007 3:43 pm

Hi All,
I'm trying to connect to SQL Server 2005 64 bit.
Using existing 4.2 DataDirect drivers.
I fail connecting to it (posting from home, so exact error will be posted later).
I was told that 64 bit SQL Server doesn't support ODBC all together

.
Does anyone have any info or experiance working with this 64bit version of SQL server 2005?
I was trying to install the latest version of DataDirect from Eservices but the tar file doesn't seem to open successfully (failing on the wizard's jar file)
Thanks in advance for your time...

DSguru2B · Post by **DSguru2B** » Mon Mar 26, 2007 3:47 pm

I connect to SQL Server 2005, just need to check if its 64 bit. Can't do that untill tomorrow. But there is an option, something to the effect "SQLServer 2000 compatable", make sure you have that enabled.

DSguru2B · Post by **DSguru2B** » Tue Mar 27, 2007 8:56 am

I confirmed it with my DBA. We do have 64bit SQL Server 2005. The driver we are using is DataDirect 5.0
I connect to it, no problem.

Ultramundane · Post by **Ultramundane** » Wed Mar 28, 2007 8:44 am

We connect to 64 bit 2005 sql server using datadirect 5.2. I was told by IBM that only 5.2 is certified for 2005. We had/have issues with dynamic porting, but it does work with static ports.

roy · Post by **roy** » Wed Mar 28, 2007 1:48 pm

Thanks for the replies

Static ports you say

I hope the DBA will know what that means

Will update on how it goes
(entering hollydays here so might take 2 weeks to confirm

)

DSguru2B · Post by **DSguru2B** » Wed Mar 28, 2007 2:50 pm

Mostly databases are set up on static ports, atleast on all sites I have seen that use SQL Server. I am guessing its the same at your place too roy.

Ultramundane · Post by **Ultramundane** » Thu Mar 29, 2007 12:10 pm

The sql server browser service is new with 2005 and it is the default configuration for sql server. I could not get the default configuration to work with the odbc driver. That is, I could not use a named instance and connect to the sql browser service to retrieve the port of the running instance. We had to avoid the browser service and directly connect to the running instance by forcing the port number in both the odbc DSN and the sql server instance.

ray.wurlod · Post by **ray.wurlod** » Thu Mar 29, 2007 3:17 pm

I can sense a DataStage (ODBC stage) enhancement request coming on. Who'd like to be first? There's a forum here for exactly that - all posts are forwarded to IBM, and we can guarantee that they are looked at there.