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

SQL Anywhere 12.0.0 (Français) » SQL Anywhere 12 - Changes and Upgrading » What's new in version 11.0.0 » SQL Anywhere

 

SQL Anywhere deprecated and discontinued features

  • FORMAT ASCII clause deprecated for LOAD TABLE, UNLOAD TABLE, INPUT, and OUTPUT statements   The FORMAT ASCII clause for the LOAD TABLE, UNLOAD TABLE, INPUT, and OUTPUT statements has been deprecated and is replaced by FORMAT TEXT. Utilities such as dbunload now generate reload scripts containing FORMAT TEXT rather than FORMAT ASCII.

    For the OUTPUT statement, the FORMAT TEXT clause now writes the data in the same file format as FORMAT ASCII did in previous versions. The output formerly created by FORMAT TEXT is no longer available.

  • Database properties   The following database properties are unsupported:

    • MapPages
    • PreserveSource
    • UniqueIdentifier

  • Server properties   The following server properties have been deprecated in this release:

    • MaxMessage
    • Message
    • MessageTime
    • MessageText
    • MessageWindowSize

  • SPX protocol unsupported   Support for the SPX protocol has been removed in this release. As a result, the following protocol options are discontinued:

    • ExtendedName protocol option [ENAME]
    • RegisterBindery protocol option [REGBIN]
    • SearchBindery protocol option [BINSEARCH]

    The following features of the SQL Anywhere .NET Data Provider are discontinued:

    • SACommLinksOptionsBuilder class: SpxOptionsBuilder property
    • SACommLinksOptionsBuilder class: SpxOptionsString property
    • SASpxOptionsBuilder class

  • dbinit -e option unsupported   The dbinit -e option, used for specifying simple encryption when creating a database, is no longer supported. Use the -ea simple option to specify simple encryption. See Initialization utility (dbinit).

  • Discontinued database options   Support for the following database options and their corresponding database properties has been removed in this release.

    Options Behavior in this release
    ansi_integer_overflow

    An overflow now always results in a SQLSTATE = 22003 - overflow error.

    When unloading, or connecting to, older databases with materialized views, the setting of this option is ignored.

    ansi_substring The behavior of the SUBSTRING function now corresponds to ANSI/ISO SQL/2003 behavior. See SUBSTRING function [String].
    automatic_timestamp New columns with the TIMESTAMP data type that do not have an explicit default value defined are never given a default value of the Transact-SQL timestamp.
    divide_by_zero_error

    Division by zero now results in an error with SQLSTATE 22012.

    When unloading or connecting to older databases with materialized views, the setting of this option is ignored.

    float_as_double

    In SQL Anywhere, the FLOAT keyword never behaves like Adaptive Server Enterprise's FLOAT keyword when a precision is not specified. SQL Anywhere does not treat FLOAT values the same as DOUBLE values.

    For Open Client and jConnect connections, this behavior is different from the default behavior in previous releases.

    When unloading or connecting to older databases with materialized views, the setting of this option is ignored.

    optimistic_wait_for_commit This option is no longer supported.
    query_plan_on_open A plan is no longer returned when an OPEN is done on a cursor. A more complete description can be obtained using the EXPLAIN statement or the PLAN function. See EXPLAIN statement [ESQL] and PLAN function [Miscellaneous].
    ri_trigger_time Referential integrity actions are now executed after the UPDATE or DELETE.
    truncate_with_auto_commit A COMMIT is now executed both before and after a TRUNCATE TABLE statement is executed.
    tsql_hex_constant Hexadecimal constants are now treated as binary typed constants.
    uuid_has_hyphens

    UUID strings now contain four hyphens.

    When unloading or connecting to older databases with materialized views, the setting of this option is ignored.

    percent_as_comment In previous releases, the percent sign (%) could be used as a comment marker depending on the setting of the percent_as_comment database option. Now, SQL Anywhere treats the % sign as a modulo operator. See MOD function [Numeric].

  • SQLANYSH10 environment variable unsupported   In previous releases, some of the SQL Anywhere software was installed into a shared directory. This location could be specified by the SQLANYSH10 environment variable. Software is no longer installed into a shared directory as part of the installation process, and the SQLANYSH10 environment variable is no longer used.

    When creating a silent install, you no longer need to set the SHARED_DIR location. See Using a silent install for deployment.

  • sa_get_server_messages system procedure discontinued   In previous releases, you could use the sa_get_server_messages system procedure to return constants from the database server messages window as a result set. You can now use the sa_server_messages system procedure to obtain this information. See sa_server_messages system procedure.

  • background_priority option deprecated   The background_priority option has been deprecated. Use the priority option instead. See priority option.

  • encrypt_aes_random_iv option unsupported   Support for the encrypt_aes_random_iv database option has been removed in this release. Now, a random IV (initialization vector) is always used.

  • DLL protocol option unsupported   Support for the DLL protocol option has been removed. Windows database servers and clients use Winsock 2.2. Windows Mobile clients use Winsock 1.1. See Using the TCP/IP protocol.

  • SQL Anywhere Broadcast Repeater utility renamed   In version 10, the command to run the SQL Anywhere Broadcast Repeater utility was dbns10. In this release, it is dbns11. See Broadcast Repeater utility (dbns12).

  • SQLANY10 and SQLANYSAMP10 environment variables renamed   The SQLANY10 and SQLANYSAMP10 environment variables have been renamed SQLANY11 and SQLANYSAMP11, respectively. See: