SAP SQL Anywhere (formerly SQL Anywhere Studio) Changelog

What's new in SAP SQL Anywhere (formerly SQL Anywhere Studio) 16.0.0.1948

• SUPPORT PACKAGE ENHANCEMENTS:
• SQL Anywhere enhancements and behavior changes:
• xp_getenv system procedure improvement—database upgrade or rebuild required The xp_getenv system procedure has been changed so that it is a procedure that runs with invoker privileges regardless of the invoker/definer setting. The procedure returns a LONG NVARCHAR value. Previously, it returned a LONG BINARY value.
• See xp_getenv system procedure.
• sa_cpu_topology system procedure improvement—database upgrade or rebuild required The sa_cpu_topology system procedure has been modified to include information about user-selected physical processors specified using the -gta database server option or the ProcessorAffinity server property. This feature allows the database server to make use of newly added processors during runtime (also know as hot-add and hot-remove).
• The restrictions and limitations for the -gt, -gta, and -gtc database server options are preserved.
• See sa_cpu_topology system procedure.
• sp_list_directory system procedure enhancements In addition to returning the path, file type, and file name of all files and directories in a specified location, the sp_list_directory system procedure now also returns the date the file was created, last modified, and last accessed, as well as the owner and any access permissions required for the file or directory.
• See sp_list_directory system procedure.
• Multiple OData Producer support This feature has been updated for build 1823.
• The OData Server now supports multiple customizable OData Producers that allow you to establish multiple database connections. Use the new embedded HTTP server option, Producers, in your OData Server configuration to create OData Producers.
• See How to configure the OData Server.
• Optimistic Concurrency Control (ETags) This feature has been updated for build 1823.
• OData Producers now support Optimistic Concurrency Control as defined by version 2.0 of the OData Specification. The concurrencytoken clause of the ENTITY OSDL statement is used to generate ETags that identify the state of an entity instance at the time the instance is requested.
• See ENTITY statement.
• OData enhancement: Search strings are restricted to 254 bytes When using OData filters—such as startswith, substringof, and indexofwith—on long search strings, searches are performed on the first 254 bytes only.
• OData enhancement: Support for proxy table insertions All key properties must be explicitly specified when creating entities in entity sets that are proxy tables in a SQL Anywhere database.
• OData enhancement: substringof return value This feature has been updated for build 1823.
• The substringof(s1, s2) filter returns whether the s1 string is a substring of s2.
• New database properties The following database properties have been added in this release:
• BackupInProgress
• TimeWithoutClientConnection
• See List of database properties.
• Support for callbacks in the SQL Anywhere C API Support for callbacks has been added to version 3 of the SQL Anywhere C API. The following function is now available when _SACAPI_VERSION is defined as 3.
• sacapi_bool sqlany_register_callback( a_sqlany_connection * sqlany_conn, a_sqlany_callback_type index, SQLANY_CALLBACK_PARM callback );
• This function can be used to register callback functions.
• JDBC The SQL Anywhere JDBC driver support for escape sequences has been enhanced to include the TIMESTAMPADD and TIMESTAMPDIFF functions.
• See ODBC escape syntax.
• ODBC The ODBC driver support for escape sequences has been enhanced to include the TIMESTAMPADD and TIMESTAMPDIFF functions. Previously, calling the ODBC SQLGetInfo function to retrieve the version of the ODBC driver (SQL_DRIVER_VER) returned a string that did not include the build number of the driver. Now, the format of the string returned is xx.yy.zzzz where xx is the 2-digit major version number, yy is the 2-digit minor version number, and zzzz is the build number (for example, 16.00.1234).
• SQL Anywhere OLE DB provider enhancements—database upgrade required Updates have been made to the SQL Anywhere OLE DB provider.
• MobiLink enhancements and behavior changes:
• Support for SAP Sybase IQ 16 The MobiLink server now supports consolidated databases running on SAP Sybase IQ 16.0 servers. For information about recommended ODBC drivers, see [external link] http://www.sybase.com/detail?id=1011880.
• dbmlsync offline transaction log retrieval has changed The dbmlsync utility can now retrieve offline transaction logs from the SQL Anywhere database server instead of accessing them directly. If offline transaction logs are required but the given offline transaction log directory cannot be opened or it does not contain offline transaction log files, then dbmlsync retrieves the offline transaction logs through the database server. The following restrictions apply:
• The user ID that is used by dbmlsync to connect to the synchronization database must have the READ FILE and WRITE FILE privileges and all the offline transaction log files must be in the online transaction log directory.
• The SQL Anywhere database server must have Support Package build number 1823 or later to support this feature.
• There is a slight performance penalty when using this feature because the database server must do more work to retrieve the pages. If performance is critical, then using the dbmlsync OfflineDirectory extended option may be best for your deployment.
• See OfflineDirectory (dir) extended option.
• dbmlsync provides the ability to restart downloads when no bytes of data have been received The dbmlsync utility now allows you to restart a failed download even if no bytes of the download have been received. Previously a download could only be restarted if at least one byte had been received.
• Synchronization models can be duplicated The Synchronization Models menu in the MobiLink plug-in has a new option to duplicate a synchronization model.
• Relay Server enhancements and behavior changes:
• Relay Server Record affinity flag now accepts a value of expired The Relay Server Record affinity flag has been extended to allow Relay Server to signal that the affinity cookie is expired.
• PRODUCT-WIDE DEPRECATED AND REMOVED FEATURES:
• Strong encryption in FIPS, TLS, and HTTPS now achieved using OpenSSL:
• SQL Anywhere version 16.0 up to build 1695 and version 12.0.1 up to build 3986 included a Certicom encryption module that provided strong encryption used throughout the software. Now, SQL Anywhere includes an OpenSSL encryption module for the strong encryption. The Certicom encryption module has been removed.
• FIPS-certified encryption on Windows Mobile no longer supported:
• Previously, FIPS-certified encryption was supported on Windows Mobile devices, but only devices that used ARM processors. This support has ended. FIPS-certified encryption is no longer supported for Windows Mobile.
• SAP JRE replaces Oracle JRE in the software:
• Previously, an Oracle JRE was shipped with the software for use by clients. Now, an SAP JRE is shipped instead.
• Upgrading overwrites the JRE directory (%SQLANY16%\binXX\jre170) and its subdirectories. If you are using certificates, then your certificate store (%SQLANY16%\binXX\jre170\lib\security\cacerts) is overwritten, including your certificates. Similarly, fonts you added to the %SQLANY16%\binXX\jre170\lib\fonts\fallback directory to help display characters in the administration tools may be lost. To minimize upgrading steps as a result of the JRE change, create a backup copy of the JRE directory and all of its subdirectories before you upgrade so that you can refer to or restore files (such as cacerts) from the backup, as needed.
• The SAP JRE may perform differently than the Oracle JRE. Use the java_vm_options option (SQL Anywhere), and/or the -sl java option (MobiLink) to optimize your Java VM startup settings.
• PRODUCT-WIDE NEW FEATURES:
• New security model: Role-based access control (RBAC):
• SQL Anywhere 16.0 introduces a new role- and privileged-based security model to replace the former authorities and permissions security model. The new role-based security model provides you with granular control over the privileged tasks that users can perform, and simpler administration of access control.
• For existing SQL Anywhere customers who are upgrading to version 16.0, backwards compatibility has been provided so that your applications will continue to function once your database has been upgraded. A special chapter has been provided for you to understand the difference between the models, what takes place automatically when you upgrade, and what you should consider doing if you have applications that use SQL Anywhere (such as updating your GRANT and REVOKE statement calls).
• LDAP USER AUTHENTICATION SUPPORT:
• SQL Anywhere now provides support for LDAP user authentication. The following list provides information on what has been added or changed to support LDAP user authentication.
• Changes to the root login policy:
• The following login policy options have been added to the root login policy to support LDAP user authentication:
• ldap_primary_server
• ldap_secondary_server
• ldap_auto_failback_period
• ldap_failover_to_std
• ldap_refresh_dn
• System procedures:
• The following system procedures have been added or enhanced to support LDAP user authentication:
• sa_get_ldapserver_status system procedure (new)
• sa_get_user_status system procedure (enhanced)
• New columns (user_dn, user_dn_cached_at, password_change_state, password_change_first_user, password_change_second_user) are reported by the sa_get_user_status system procedure.
• Database server and database options:
• The following database options have been added or enhanced to support LDAP user authentication:
• login_mode option
• SQL statements:
• The following SQL statements have been added to support LDAP user authentication:
• CREATE LDAP SERVER statement
• ALTER LDAP SERVER statement
• DROP LDAP SERVER statement
• VALIDATE LDAP SERVER statement
• The following SQL statements have been enhanced to support LDAP user authentication:
• ALTER USER statement (new REFRESH DN syntax)
• CREATE LOGIN POLICY statement (new login policy options)
• ALTER LOGIN POLICY statement (new login policy options)
• COMMENT statement (ability to comment on LDAP server configuration objects)
• trusted_certificates_file option
• Catalog changes:
• The following catalog changes have been made to support LDAP user authentication:
• SYSLDAPSERVER system view (new) The SYSLDAPSERVER system view contains one row for each LDAP SERVER object configured in the database. See SYSLDAPSERVER system view.
• SYSUSER system view The SYSUSER system view has two new columns related to LDAP user authentication: user_dn and user_dn_cached_at. See SYSUSER system view.
• PRODUCT-WIDE BEHAVIOR CHANGES:
• Sample certificates are located in a new directory Sample X.509 certificates used for TLS communication have been moved from the bin32 and bin64 directories to the C:\Users\Public\Documents\SQL Anywhere 16\Samples\Certificates directory.
• The following files have also been added to the new directory:
• rsaclient.id
• rsaclient_nopwd.id
• rsaroot.key
• rsaserver_nopwd.id
• SQL Anywhere supports TLS version 1.1:
• SQL Anywhere server and client libraries now support TLS version 1.1 for both TLS connection encryption and HTTPS. TLS version 1.1 is not supported on Mac OS X.
• iAnywhere Solutions Oracle ODBC driver renamed:
• For version 16.0, the SQL Anywhere Oracle ODBC driver name is SQL Anywhere 16 - Oracle. The previous version was called iAnywhere Solutions 12 - Oracle. For reference, the SQL Anywhere ODBC driver name is SQL Anywhere 16.
• PRODUCT-WIDE DEPRECATED AND REMOVED FEATURES:
• Elliptic curve encryption:
• Support for ECC encryption has been removed. This change affects the following features:
• The IsEccAvailable server property has been removed.
• The -ec database server option no longer accepts ECC for the TLS_TYPE protocol option. The TLS_TYPE protocol option for the -ec database server option has been removed from the documentation; however, this option is still supported by the software for backwards compatibility.
• The ENCRYPTION connection parameter no longer accepts ECC for the TLS-TYPE argument. The TLS_TYPE argument for the ENCRYPTION connection has been removed from the documentation; however, this option is still supported by the software for backwards compatibility.
• The Certificate Creation utility (createecert ) no longer accepts the -ec option and the -t option no longer accepts ecc for the encryption type.
• The Key Pair Generator utility (createkey) only creates RSA key pairs. The Choose encryption type and Enter ECC curve prompts have been removed.
• The SQL Anywhere Monitor does not support ECC encryption. To monitor a pre-version 16 MobiLink server that uses ECC encryption, you must:
• Start the MobiLink server with a second set of network protocol options that does not use ECC.
• Add the MobiLink server as a resource to be monitored. When prompted to specify the port number for the MobiLink server resource, specify the number that is not associated with ECC encryption.
• The MobiLink tls_type protocol option no longer accepts ECC for the tls_type option. The MobiLink tls_type protocol option has been removed from the documentation; however, this option is still supported by the software.
• The MobiLink client e2ee_type protocol option no longer accepts ECC for the tls_type option. The MobiLink client e2ee_type protocol option has been removed from the documentation; however, this option is still supported by the software.
• The Outbound Enabler tls_type option no longer supports ECC as a choice. The tls_type protocol option has been removed from the documentation.
• UltraLite C/C++ and UltraLiteJ API methods and properties related to ECC configuration have been removed.
• Send column names:
• n MobiLink and UltraLite, column names are now always sent during synchronization. Attempts to disable sending column names are ignored. This change affects the following features:
• In MobiLink, the SendColumnNames (scn) extended option for dbmlsync has been deprecated and is ignored if set to OFF. The SendColumnNames extended option has been removed from the documentation; however, this option is still supported by the software.
• UltraLite and UltraLiteJ clients always send column names when synchronizing with a MobiLink server database. Methods and approaches that are used to stop sending column names are now ignored and deprecated. The following members and parameters are affected:
• Send Column Names synchronization parameter
• Synchronization profile options
• SyncParms.setSendColumnNames method [UltraLiteJ]
• SyncParms.getSendColumnNames method [UltraLiteJ]
• ULSyncParms.SendColumnNames property [UltraLite.NET]
• send_column_names in the ul_sync_info structure [UltraLite C and Embedded SQL datatypes]