June 11, 2009 at 11:23 pm
Hi Guys,
I am migrating our database server from SQL server 2005 32 bit SP2 to SQL server 2005 64 bit SP3. I have migrated one database and the application is running fine, all tested. But one thing i want to know that we have got some users which connect to the server using ODBC connection. So do i have to worry about the ODBC connection when i migrate the database??
If yes, then how can i configure the ODBC connection form a 32 bit client machine to the 64 bit SQL server 2005? Are there any known issues regarding to this topic?
Please let me know. Thank you very much in advance.
June 12, 2009 at 2:23 am
June 15, 2009 at 12:04 am
I had a look to that link but it didn't clear my problem. My problem is like Migrated from 32 bit to 64 bit and users machine are XP and they were able to connect to 32 bit sql server 2005 before but once i migrated database to the 64 bit sql server 2005 the application is working fine but the users/clients who were using the ODBC connection on their XP machine to the sql server are not able to connect. Can this be an ODBC issue?
June 15, 2009 at 4:00 am
Any specific error message
June 16, 2009 at 6:52 am
zombi (6/15/2009)
I had a look to that link but it didn't clear my problem. My problem is like Migrated from 32 bit to 64 bit and users machine are XP and they were able to connect to 32 bit sql server 2005 before but once i migrated database to the 64 bit sql server 2005 the application is working fine but the users/clients who were using the ODBC connection on their XP machine to the sql server are not able to connect. Can this be an ODBC issue?
Did the machine name or IP address change? And are the client machines pointed to this new address if it changed?
Are they using Windows or SQL authentication?
Can you connect remotely as yourself? And then as a user?
Greg E
June 16, 2009 at 5:55 pm
the database was able to send an email before but now it is not able to send any mail through it. I suspect that sql database was using any MAPI session and it is not configures for new server. can this be a issue?
Sorry i do not have error messages to post.
July 10, 2009 at 12:55 pm
I am dealing with the same issue. We have several applications that share a database. The core application has been upgraded to .NET and that database has been upgraded to a 64 bit SQL server. However, there remains several legacy VB6 applications that require ODBC DSN settings to that database, running on Windows XP (32 bit) SP 3.
Now we cannot create the DSN settings to point to the new SQL (64 bit). Database server is Windows 2003 Server with SQL Server 2005 64 bit.
The error that is returned when a user DSN setting is being created:
Using TCP/IP
========================
Connection Failed:
SQLstate: '01000'
SQL Server Error: 14
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen(Invalid Instance())
Connection Failed:
SQLstate: '08001'
SQL Server Error: 14
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Invalid connection.
Using Named Pipes
=========================
Connection Failed:
SQLstate: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen(Connect())
Connection Failed:
SQLstate: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.
Users have been added to the AD user group for proper access to the SQL db.
Should the native Windows XP 32 bit ODBC Data Source Administration be able to setup DSN setting connections to a 64 bit SQL server?
Is there some special configuration I need to tell the DBAs to set/check on the server side to allow 32 bit ODBC connections??
Thanks -
Nathan Synan
July 10, 2009 at 3:06 pm
We have a mixed environment and ODBC works fine in both. Have you checked the security and setup is the same on the 64 bit server?
July 10, 2009 at 3:39 pm
Your client PC's are running an x86 OS - and therefore require an x86 driver to connect to a database. The client PC does not care, nor even know anything at all about the OS hosting the database you are connecting to.
That database could be Oracle, SQL Server, Intersystems Cache, DB2, Pervasive, PostGreSQL, MySQL, etc... Those databases can be hosted on Linux, AIX, HP OpenVMS, Windows, BeOS, or any other OS running x86, x64 or IA64 architectures.
To connect to one of the above, you only need to have the correct ODBC drivers for that database system. You can use the same 32-bit Oracle client to connect to your Oracle databases on your AIX 64-bit machines as you use to connect to your Oracle instances running on Red-Hat Linux x86. As long as you are not trying to use the Oracle 8 drivers to connect to an Oracle 11g system 🙂
The errors that you are getting are most likely caused by the name change of the server\instance of SQL Server. Those PC's probably are trying to connect to the old server - which does not exist.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
July 12, 2009 at 5:56 pm
This Might help :
Database products on Windows typically offer an OLE DB or ODBC data source provider -- a piece of middleware registered with the system that allows any application that supports OLE DB to talk to that data source. Most of us ought to be familiar with this mechanism, and both the 32-bit and 64-bit editions of SQL Server have their own data providers.
Keep a few things in mind when you're using the 64-bit edition of SQL Server and 64-bit ODBC drivers. First, 32-bit programs cannot see 64-bit ODBC drivers -- they can only see other 32-bit applications, including 32-bit ODBC drivers. The Jet database engine, for instance, does not have a 64-bit driver available; it will only run in 32-bit space and talk to 32-bit ODBC connectors.
You should, however, be able to use the 32-bit driver to talk to a 64-bit database application, for the same reason you'd be able to connect to a remote data server regardless of what it's running. If the actual connection to the database server is performed through a mechanism like TCP/IP or named pipes, those things aren't dependent on a specific architecture. Hence, they should work across 32- and 64-bit environments. (Note that there may be some issues with linking a 32-bit instance of SQL Server to a 64-bit instance via distributed queries, if you're trying to do that.)
If you're using 64-bit Windows and want to edit the configuration of the 32-bit ODBC drivers, you can do this by launching the program %SystemRoot%\SysWOW64\odbcad32.exe, which brings up the 32-bit ODBC console. The default ODBC interface, the one invoked from the Control Panel, is 64-bit only.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply