Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SAP Sybase SQL Anywhere 16.0 » SQL Anywhere 16 - Changes and Upgrading » What's new in version 12.0.0


SQL Anywhere deprecated and discontinued features


As with all forward-looking statements, the lists of deprecated features are not guaranteed to be complete and are subject to change.

  • Address Windowing Extensions (AWE) deprecated   The use of Address Windowing Extensions for 32-bit Windows is deprecated. If you need a large cache, it is recommended that you use the 64-bit version of the SQL Anywhere database server on a 64-bit operating system.

  • CALL statement   Use of this statement to invoke a function is deprecated. If you have a function you want to call, consider using an assignment statement to invoke the function and assign its result to a variable. For example:
    DECLARE varname INT; SET varname=test( );

    See CALL statement.

  • STOP ENGINE statement   The STOP ENGINE statement is deprecated. Use the STOP SERVER statement instead. See STOP SERVER statement.

  • Windows 2000 support removed   As of version 12.0.0, SQL Anywhere is no longer supported on Windows 2000.

  • Rebuild utility removed   The Rebuild utility is not supported in this release for rebuilding SQL Anywhere databases. You can rebuild databases using the Unload utility (dbunload). See Unload utility (dbunload).

  • Unsupported database properties   The following properties have been removed in this release:

    • CheckpointLogBitmapPagesWritten database property
    • CheckpointLogBitmapSize database property
    • java_main_userid connection property
    • QueryRowsBufferFetch connection property
    • QueryRowsBufferFetch database property

  • JDBC-based server classes deprecated   Support for the following JDBC-based server classes has been deprecated:

    • IQJDBC
    • SAJDBC

    Applications should be updated to use the ODBC-based server classes. See ODBC external server definitions.

  • SQL Anywhere Explorer no longer supported   The SQL Anywhere Explorer and SQL Anywhere Toolbar for Visual Studio are no longer supported. Use Microsoft's Server Explorer instead.

  • Short int embedded SQL indicator variable deprecated   To allow for the future use of 32- and 64-bit lengths and indicators, the use of short int for embedded SQL indicator variables is deprecated. Use a_sql_len instead. See Indicator variables.

  • EngineName (ENG) connection parameter deprecated   The EngineName (ENG) connection parameter is deprecated. You can use the ServerName (Server) connection parameter instead. The short form of the ServerName connection parameter has been changed from ENG to Server. See ServerName (Server) connection parameter.

  • iAnywhere JDBC driver deprecated   The Type 1 iAnywhere JDBC driver is deprecated. Use the Type 2 SQL Anywhere JDBC driver instead. See New SQL Anywhere TYPE-2 JDBC driver.

  • -gu all database server option deprecated   The value all for the -gu database server option is deprecated. See -gu database server option.

  • -sm dbsrv12 database option (deprecated)   The -sm database option is deprecated. Use the CREATE MIRROR SERVER statement instead. See CREATE MIRROR SERVER statement.

  • SET OPTION statement   The ability to specify an identifier as an option value in a SET OPTION statement, rather than a string literal, has been deprecated.

  • Service utility (dbsvc utility)   The value Standalone for the -t option has been deprecated. Use -t Personal instead to create a service for the personal database server. See Service utility (dbsvc) for Linux and Service utility (dbsvc) for Windows.

  • Host (IP) protocol option support from the server   Support for specifying the Host (IP) protocol option in a server command has been removed. For example, the following command is no longer supported and now returns an error: dbeng12 -x tcpip(host=host-name) "%SQLANY12%\demo.db". However, you can still specify the Host (IP) protocol option in a CommLinks(LINKS) connection parameter from the client side. See Host (IP) protocol option (client side only).


    The Host protocol option is different from the Host connection parameter. The Host protocol option is used by the CommLinks connection parameter. You should only use the CommLinks (LINKS) connection parameter if you need to specify TCP/IP options other than Host and ServerPort (PORT). You cannot specify both CommLinks and Host in the connection string. See CommLinks (LINKS) connection parameter.

    In most cases, you should use the HOST connection parameter. See Host connection parameter.