I originally posted this a few years ago to help people configure their Java applications to use the iAnywhere JDBC driver, which was replaced by the SQL Anywhere JDBC driver in SQL Anywhere version 12. I am reposting it here with a few minor updates, since I still refer to it occasionally and I think it is still useful.
- Sql Anywhere 17 Odbc Driver
- Sql Anywhere 12 Driver Download
- Sql Anywhere 12 Driver
- Sql Anywhere 12 Odbc Driver Install
SQL Anywhere 12 64-bit client deployment is a program developed by iAnywhere. The software installer includes 97 files. A majority of the PCs this is running on, most OS versions are Windows 7 (SP1). The distribution of this has mostly been seen in the United States. For 64-bit Windows, the 32-bit ODBC driver registry entries ('SQL Anywhere 12 - custom-name ' and 'ODBC Drivers') are located under the following key: HKEYLOCALMACHINE SOFTWARE Wow6432Node ODBC ODBCINST.INI To view these entries. I would like to build a database that I can easily use with any programming language. I would like to get this done on ODBC. Does anyone there have an idea where I can get SQL anywhere 12 ODBC driver? Kindly include a little note on how to have it up.
I have heard from customers that connecting to SQL Anywhereover JDBC can be difficult at times. In my investigations of this, I have found that this is almost always due to confusion over the classname to use to register the JDBC driver, and the URL’s to use to actually connect to the database. In stepping back, I can see how people might easily get confused based on the history of the JDBC driver. Here is my attempt to clarify things by following the history of the driver, starting with SQL Anywhere version 9.
Before I go into detail on the history of the SQL Anywhere JDBC driver, here is a table which explains classpath settings, jar files required, driver name URLs and sample connection URLs.
SQL Anywhere Version | JDBC jar file to include in classpath | Driver classname | Connection URL |
---|---|---|---|
9.0.2 | %ASA90%javajodbc.jar | ianywhere.ml.jdbcodbc.IDriver | jdbc:odbc:Driver=Adaptive Server Anywhere 9.0;UID=DBA;PWD=sql;eng=demo |
10.0.0 | %SQLANY10%javajodbc.jar | ianywhere.ml.jdbcodbc.jdbc3.IDriver | jdbc:odbc:Driver=SQL Anywhere 10 Demo;UID=DBA;PWD=sql;eng=demo |
10.0.1 | %SQLANY10%javajodbc.jar | ianywhere.ml.jdbcodbc.jdbc3.IDriver | jdbc:ianywhere:Driver=SQL Anywhere 10;DSN= SQL Anywhere 10 Sample |
11.0.0 | %SQLANY11%javajodbc.jar | ianywhere.ml.jdbcodbc.jdbc3.IDriver | jdbc:ianywhere:Driver=SQL Anywhere 10;DSN= SQL Anywhere 11 Sample |
11.0.1 | %SQLANY11%javasajdbc.jar | sybase.jdbc.sqlanywhere.IDriver | jdbc:sqlanywhere:uid=DBA;pwd=sql;eng=demo |
12.0.0 | %SQLANY12%javasajdbc4.jar | no longer required for JDBC 4.0 | jdbc:sqlanywhere:uid=DBA;pwd=sql;eng=demo |
16.0 | %SQLANY16%javasajdbc4.jar | no longer required for JDBC 4.0 | jdbc:sqlanywhere:uid=DBA;pwd=sql;eng=demo |
- Adaptive Server Anywhere version 9.0 (aka SQL Anywhere 9.0)
In version 9, SQL Anywhere supported JDBC 2.0 using an iAnywhere generic JDBC-ODBC bridge driver (similar to but different from the Sun JDBC/ODBC driver). The jar file is jodbc.jar, and resides in the %ASA90%java directory. To use the iAnywhere JDBC driver, you need to include the jar in your classpath. Then, you need to register it in your java app using the following code:Since the iAnywhere JDBC/ODBC driver is a bridge driver, to connect to your SQL Anywhere database, you need to specify a “DRIVER=” parameter along with the rest of your connect string. For example:or, you could use an ODBC data source like this:The MS Word monthly calendar format can be edited, adding your own events, notes, appointment and print.☼ JPG version: Free download ZIP file (contains 12 image files), unzip and open it in Windows Image Viewer or another program that can display the JPG file format and print. Free monthly calendars that can be edited. ☼ PDF version: You can download free and open it in Acrobat Reader or another program that can display the PDF file format and print.☼ DOC and DOCX version: just free download, open it in MS Word, LibreOffice, Open Office, Google Doc, etc. - SQL Anywhere 10.0.0
In version 10, we added support for JDBC 3.0. To use the version 10 iAnywhere JDBC/ODBC bridge driver, you need to again include %SQLANY10%javajodbc.jar in your classpath. However, the class name for driver registration is slightly different:Once registered, the connection URL was the same as in verison 9, above.While you will not be able to claim features controlled by another player, this option may allow you to share in the benefits of features claimed by opposing players.Only one follower may be deployed per turn, and this wooden figure comes from the player’s color-coded pool. Carcassonne board game strategy rules. If the tile cannot be legally played, the tile is discarded and a new one is drawn.After placing a tile, a player may then elect to place a follower there. - SQL Anywhere 10.0.1
After version 10 was released, we noticed that in some customer issues involving JDBC, the iAnywhere driver was not always being loaded when it was supposed to be, particularly when the Sun JDBC/ODBC bridge driver was present. It turns out that our use of “jdbc:odbc” in the connection URL was not sufficient to guarantee that the iAnywhere driver would be used during a connection. If the Sun bridge were present, it could be picked up and used instead, which lead to all sorts of unexpected behaviour. To resolve this problem, the 10.0.1 maintenance release introduced a new URL header for the iAnywhere driver, “jdbc:ianywhere”. From this point forward, the URL to register the driver was the same as with v10, but the correct URL to use when connecting to the database was as follows:The “jdbc:ianywhere” portion of the connection string was actually back-ported to a 9.0.1 ebf, so if you are running one of the later 9.0.1 or 9.0.2 ebfs, the above connection URL will work for you as well. - SQL Anywhere version 11.0.0
In SQL Anywhere version 11, there was no change in classname for the driver or URL for the connection string, but we did update to a newer version of the JDK. This meant we had to drop the JDBC 2.0 driver, because JDK 1.4 and newer no longer supported it. To make things easier for our customers, we kept the JDBC 2.0 class names in the version 10 JDBC 3.0 jar. They simply pointed to the JDBC 3.0 equivalents. - SQL Anywhere 11.0.1
In SQL Anywhere version 11.0.1, a new SQL Anywhere JDBC driver was introduced. No longer a generic iAnywhere JDBC driver, it is a JDBC driver specific to SQL Anywhere. This was done to make it easier (ie. less confusing) for people to use JDBC with SQL Anywhere. With the new driver, there is no need to install ODBC on the system. This wasn’t a problem for Windows, but our Linux and Unix customers often had problems with this. As an added bonus, the performance of the driver was improved slightly because we no longer have to go through the ODBC driver manager. This change involved adding 2 new files to the SQL Anywhere installation: sajdbc.jar and dbjdbc11.dll. To use the new driver, you need to include %SQLANY11%javasajdbc.jar in your classpath. Then, the driver registration is as follows:Then, to connect, you use the following URL:9 Tier Capacity – up to 27 Patient Drawers. The compact 800 Series Cart puts every inch of its compact frame to efficient use to get nurses closer to their patient. It’s a practical companion to units with automated dispensing cabinets or in situations where floor space is limited.Features:.Designed for units with a lower patient to nurse ratio to provide a good mix of medications and supplies. - SQL Anywhere 12/16
SQL Anywhere 12 deprecated the use of the iAnywhere JDBC/ODBC bridge driver in favor of the new SQLAnywhere driver. In addition, SQL Anywhere 12 will support JDBC 4.0 (which requires JDK 1.6 or newer). To continue to use the JDBC 3.0, users do not have to make any changes from previous versions. However, to use the JDBC 4.0 support, the new driver name is “sybase.jdbc4.sqlanywhere.IDriver”, and requires that %SQLANY12%javasajdbc4.jar be in your classpath. However, there is no need to call DriverManager.registerDriver(…) to register the driver before using it anymore. Sun has implemented automatic driver registration so that applications just need to make sure that sajdbc4.jar is in the classpath (and dbjdbc12.dll is in the path), and use the “jdbc:sqlanywhere” URL header to connect. So, to connect with SQL Anywhere 12 and JDBC 4.0, all you need is something like the following line of code:
That concludes our history lesson. Confused yet?
Sql Anywhere 17 Odbc Driver
Hi,![Sql anywhere 12 odbc driver Sql anywhere 12 odbc driver](/uploads/1/2/5/0/125051123/742204941.png)
I work for a software company that provides membership and member data management software. When we get new clients, I take what ever data sources they have, be they simple excel documents or CSV files or a completely unheard of yet comprehensive database solution, and then convert/migrate the data into our web based database.
One database solution that rarely comes up, ReMEMBER, uses a Sybase database for the data backend. Previously, I have managed to get open the remember.db database file via either an SQL Anywhere 10 or 11 ODBC driver I managed to get by downloading trial version sof SQL Anywhere 10 and 11.
Installing those gave me the needed ODBC drivers, and I was able to access the database and extract the raw tables for use in migrating to our database schema.
The problem now, is that neither the SQL Anywhere 10 or 11 ODBC drivers work for this current remember.db database file; both ODBC drivers fail on the Test Connection while setting up the new User Data Source in the Data Sources (ODBC) tool. (I am using XP Pro)
Sql Anywhere 12 Driver Download
The only error message I have to go off of simply tells me it can't access the data source because it was made with another version of the software.![Full Full](/uploads/1/2/5/0/125051123/110536291.png)
On the few other times I have had to rip raw data from ReMEMBER datafiles, sometimes SQL Anywhere 10 would work, sometimes SQL Anywhere 11 would. Now both tell me the database file was made with a different version of the software.
So I guess my question is, is there any easy way to tell, or any easy tool to tell what version of ODBC driver I would need to use given the remember.db file? Any idea where I might be able to find bundled group of ODBC drivers for the various versions and flavors of Sybase products?