Any issues with SQL Anywhere 12.0.1 with Version 11 ODBC Clients?

[glenn_barber]

We have a installation with SQL anywhere 11 on an Intel 32 bit Server with about 60 windows clients using ODBC access scattered around the company.

The company wants to move to SQL Anywhere 12.0.1 on Windows 64 bit in a virtual environment.

There are no changes to the database schema or application being made.

Can we safely move the Server to SQL Anywhere 12.0.1 and continue to keep some or all of the users on the existing V11 32 Bit ODBC Client Drivers. (not changing the ServerName)

Additionally, is there a simple way to deploy new 32 Bil Version 12 ODBC Client drivers and Connection specification in the enterprise without having to execute msi's on each machine?

[chris_keating]

Your existing DSNs should continue to work provided it is not using anything that uniquely identifies the machine hosting the database (i.e., HOST=<machine_name_or_ip> ).

Deployment does not require going through an installer. You can manually copy the required files into the deployment and run

 c:\\windows\\SysWOW64\\regsvr32 %sqlany12%\\bin32\\dbodbc12.dll

This will install the 32 bit ODBC driver. The dbdsn command line utility can be used to create the DSN for your application.

[Former Member]

More details on required files and configuring the ODBC driver can be found in the doc under deploying ODBC clients.

[MCMartin]

I don't have a problem to access a V12 DB with V11 odbc even if host=... is used, so where would you see a problem with the host parameter?

[chris_keating]

The question indicated that the host is being changed to a vitual machine. If the DSN is using the HOST=, it must to updated to the host name or ip of the virtual machine.