ADO.NET 2.0 support   The ADO.NET driver has been updated to support version 2.0 of the .NET framework. Several new classes and methods have been added as part of this support. See Namespace.

SQL Anywhere Explorer   The SQL Anywhere Explorer lets you connect to SQL Anywhere databases from within Visual Studio .NET. In addition, you can open Sybase Central and Interactive SQL directly from Visual Studio .NET.

iAnywhere JDBC driver supports JDBC 3.0   The iAnywhere JDBC driver now supports JDBC 3.0 calls. The iAnywhere JDBC driver no longer supports JDBC 2.0. Both the ianywhere.ml.jdbcodbc.IDriver and ianywhere.ml.jdbcodbc.jdbc3.IDriver classes are still supported to allow existing applications to continue running without modification, but, both drivers are now identical and implement JDBC 3.0 only. You can no longer use JRE versions earlier than 1.4 with the iAnywhere JDBC driver. See JDBC support.

iAnywhere JDBC driver supports the SQL Server Native Client ODBC driver   The iAnywhere JDBC driver now checks if the ODBC driver is the Microsoft SQL Server Native Client ODBC driver and appropriately sets the default result set type and other attributes.

Support for PreparedStatement.addBatch method   The iAnywhere JDBC driver now supports the PreparedStatement.addBatch method. This method is supported for batched (or wide) inserts.

Support for SQL_GUID added to ODBC driver   Support for UNIQUEIDENTIFIER columns has now been added to the SQL Anywhere ODBC driver. A UNIQUEIDENTIFIER column can now be typed as SQL_GUID.

Support for GUID escape sequences added to ODBC driver   Support for GUID escape sequences has been added to the SQL Anywhere ODBC driver. GUID escape sequences may be used in SQL statements prepared and executed through ODBC. A GUID escape sequence has the form {guid 'nnnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnn'}.

ODBC message callbacks are now per-connection   ODBC has supported message callbacks since Adaptive Server Anywhere version 9.0.0, but messages for all connections came to a single callback function. As of version 9.0.2, when you designate a message callback function, it applies only to a single connection. This is consistent with how DBLIB works. All messages now funnel through a single function in the ODBC driver, which filters the messages by connection, and only calls the connection's callback function for those connections that have one.

New functions added to the SQL Anywhere PHP module   The following new functions have been added to the SQL Anywhere PHP module:

• sqlanywhere_execute
• sqlanywhere_error
• sqlanywhere_errorcode
• sqlanywhere_insert_id

In addition, two new options have been added to the sqlanywhere_set_option function: verbose_errors and row_counts. See SQL Anywhere PHP API reference.

Enhancements to db_locate_servers_ex function   The db_locate_servers_ex function supports two new flags: DB_LOOKUP_FLAG_ADDRESS_INCLUDES_PORT, which returns the TCP/IP port number in the a_server_address structure passed to the callback function, and DB_LOOKUP_FLAG_DATABASES, which indicates that the callback function is called once for each database or database server that is found. See db_locate_servers_ex function.

Perl DBD::ASAny driver for the Perl DBI module renamed   The Perl driver has been renamed from DBD::ASAny to DBD::SQLAnywhere. Perl scripts that use SQL Anywhere must be changed to use the new driver name. The cursor attribute ASATYPE, which returns native SQL Anywhere types has not changed, and neither have the type names (ASA_STRING, ASA_FIXCHAR, ASA_LONGVARCHAR, and so on). See Perl DBI support.

SQL preprocessor (sqlpp) -o option values   The sqlpp -o option now accepts WINDOWS rather than WINNT for Microsoft Windows. As well, you can specify UNIX64 for supported 64-bit Unix operating systems. See SQL preprocessor.