When you access remote servers defined with JDBC-based classes, consider that:
For optimum performance, an ODBC-based class is recommended (saodbc or aseodbc).
Any remote server that you access using the ASEJDBC or SAJDBC server class must be set up to handle a jConnect 6.x-based client.
If a JDBC remote server connection is disconnected or lost, you only find out that the server is unavailable if you attempt to use the JDBC remote server to access a proxy object, such as a proxy table or proxy procedure. ODBC does not have this limitation.
Discuss this page in DocCommentXchange.
|Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1|