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 16.0 » SQL Anywhere behavior changes


SQL statement behavior changes

Following is a list of SQL behavior changes introduced in SQL Anywhere version 16.0.

  • ALTER DATABASE statement   By default, the database is now stopped and restarted after an upgrade. To prevent the database from restarting, use the RESTART OFF clause to stop the database after the upgrade. See ALTER DATABASE statement.

  • SELECT * supported in view definitions   In previous releases, SELECT * was only supported in the main query of the CREATE VIEW statement. Now it is supported in the main query, a subquery, a derived table, or a subselect of the CREATE VIEW statement. See CREATE VIEW statement.

  • START DATABASE statement   The ON clause of the START DATABASE statement is deprecated. The START DATABASE statement can only start databases on the current database server. Previously, you could use the ON clause in Interactive SQL to specify a database server to use. See START DATABASE statement.

  • ALTER SERVER statement   The CONNECTION CLOSE clause of ALTER SERVER statement is not supported. Use the DROP REMOTE CONNECTION statement. See DROP REMOTE CONNECTION statement.

  • LOAD TABLE statement  

    • STRIP ON clause   The STRIP ON clause of the LOAD TABLE statement is not supported. Use the STRIP RTRIM clause instead. See LOAD TABLE statement.

  • SYSUSER system view now stores standalone role information   Previously, the SYSUSER system view stored only users in the system. Now, standalone roles (roles not associated with a user) are also stored in this view as well. However, only the user_id, object_id, user_name, and user_type columns are meaningful for these roles. See SYSUSER system view.