ODBC driver for SQL Anywhere

[Former Member]

I want to transfer data from a SQL Anywhere database to a Microsoft SQL Server database on a second computer.  The second computer is running Windows Server 2008R2 and the only application installed on it is Microsoft SQL Server 2008.

I believe I could do this if I had on ODBC driver for SQL Anywhere installed on the second computer.

Where can I find an ODBC driver for SQL Anywhere?   I am not sure of the version of SQL Anywhere.   Do the ODBC drivers for SQL Anywhere support multiple version of SQL Anywhere?

[former_member188493]

Presumably you have access to the computer with the running SQL Anywhere database. That computer should contain all the files necessary for deploying an ODBC driver to another computer. You need to determine the SQL Anywhere version, and from that you can find the documentation describing how to deploy (copy) ODBC driver files.

To find the version number, find the SQL Anywhere installation directory; for example: C:\Program Files\SQL Anywhere 16\Bin64

The folder name tells you the version: 16

Then look in the Version 16 documentation: ODBC driver required files

If you are still having trouble, tell us  the SQL Anywhere version number.

[Former Member]

The version of SQL Anywhere being used is 5.50 Build 2817.   The version of Windows is XP.

The requirement is to connect to this database from a remote computer, extract data from this database and store it in a Microsoft SQL Server Database on the same remote computer.

I don't think there are any install kits on the SQL Anywhere computer.  This SQL Anywhere is embedded as part of an analytical instrument.

Does SQL Anywhere 5.5 support client ODBC access from a remote computer?  If yes, where can I find the ODBC driver?  The remote computer has a Windows 2008 R2 operating system.

[former_member188493]

Do you have a user id and password for the embedded SQL Anywhere database? Without that, discussions about access are moot, ODBC or otherwise... nobody can help you.

Is this a one time data transfer? If so, then using the UNLOAD TABLE statement via ISQL to create tab or comma-delimited files might be easier than struggling with the ancient Version 5 client setup... assuming you have ISQL on this embedded database.