We have a remote Sybase db that provides only an odbc driver. Our Java application runs on a separate machine. I assume I need a Type 3 JDBC driver where the proxy on the db machine needs a jdbc/odbc bridge to Sybase. Is this feature supported by SQL Anywhere? If not, I'd really appreciate if someone could point me in the right direction.
Thanks a ton.
asked 14 Jun '11, 20:42
If you are using ASE, then you can use the jConnect JDBC driver that is available with ASE. Note that jConnect is a Type-4 driver so there is no need for ODBC or any other native component. If you are using SQL Anywhere, then you can use the SQL Anywhere JDBC driver that came with your copy of SQL Anywhere. In SQL Anywhere 12, the SA JDBC driver is a Type-2 driver and does not require any ODBC component. In SQL Anywhere 11 and below, the SA JDBC driver (known as the iAnywhere JDBC driver in these older versions) is a Type-1 driver and will happily work with the SQL Anywhere ODBC driver that came with your version of SQL Anywhere. There is no officially supported Type-3 JDBC driver for either SQL Anywhere or ASE.
One final note, the jConnect driver that I mentioned above for ASE also works with SQL Anywhere. If you are using SQL Anywhere, and if your particular environment demands a pure JAVA driver (which jConnect is since it is a Type-4 driver), then you can go ahead and use jConnect with SQL Anywhere. I should point out though, that in general we recommend that you use the SQL Anywhere JDBC driver with SA since it tends to be better geared towards SA and generally performs better than jConnect WHEN talking to SA. But, if you are using ASE, then you have NO choice but to use jConnect with ASE. Note that jConnect is geared towards ASE and performs quite well when talking to ASE.
answered 15 Jun '11, 07:58