Following is a list of new and enhanced SQL statements introduced in SQL Anywhere version 16.0.
ALTER TABLE statement You can now alter the owner of a table. When altering a table owner, you have the options of preserving or dropping owner permissions and preserving or dropping foreign keys. See ALTER TABLE statement.
CREATE CERTIFICATE and DROP CERTIFICATE statements You can now store certificates in the database. The CREATE CERTIFICATE statement can be used to add or replace certificates to a database. The DROP CERTIFICATE statement can be used to remove certificates from a database.See CREATE CERTIFICATE statement and DROP CERTIFICATE statement.
CREATE EVENT and ALTER EVENT statements Now, events can run on mirror servers and copy nodes in mirroring and read-only scale-out systems. To create an event that can run on any server, specify the FOR ALL clause with the CREATE EVENT statement or the ALTER EVENT statement. See CREATE EVENT statement and ALTER EVENT statement.
CREATE FUNCTION statement [Web service] You can now specify a certificate stored in the database using the certificate_name option of the CERTIFICATE clause. You can also now specify a keep-alive timeout criteria option (kto) to instantiate and cache a keep-alive HTTP/HTTPS connection for a period of time. See CREATE FUNCTION statement [Web service].
CREATE INDEX statement You can now specify WITH NULLS DISTINCT when executing the statement. See CREATE INDEX statement.
CREATE PROCEDURE statement [Web service] You can now specify a certificate stored in the database using the certificate_name option of the CERTIFICATE clause. You can also now specify a keep-alive timeout criteria option (kto) to instantiate and cache a keep-alive HTTP/HTTPS connection for a period of time. See CREATE PROCEDURE statement [Web service].
CREATE SERVER statement The USING clause DELIMITER option is used to force the use of either a slash (/) or backslash (\) as a path separator in the file names returned by the directory access server. See CREATE SERVER statement.
CREATE TEXT INDEX statement You can now create text indexes on materialized views. Use the IMMEDIATE REFRESH clause to create a text index on a materialized view. See CREATE TEXT INDEX statement.
DROP REMOTE CONNECTION statement The DROP REMOTE CONNECTION statement drops remote data access connections to a remote server. See DROP REMOTE CONNECTION statement.
CREATE TEMPORARY TRACE EVENT SESSION statement Creates a user trace event session. See CREATE TEMPORARY TRACE EVENT SESSION statement.
CREATE TEMPORARY TRACE EVENT Creates a user trace event that persists until the database is stopped. See CREATE TEMPORARY TRACE EVENT statement.
ALTER TRACE EVENT SESSION statement Adds or removes trace events from a session, adds or removes targets from a session, or starts or stops a trace session. See ALTER TRACE EVENT SESSION statement.
DROP TRACE EVENT statement Drops a user-defined trace event. See DROP TRACE EVENT statement.
DROP TRACE EVENT SESSION statement Drops a trace event session. See DROP TRACE EVENT SESSION statement.
LOAD TABLE statement For the load-option clause, you can now specify the following:
ALLOW ERRORS clause Allows you to specify the number of errors allowed before the load operation rolls back. The default is 0.
ROW LOG clause If an error is encountered while inserting or parsing a row, the database server writes an image of the input row to the specified location in addition to reporting the row to the user.
MESSAGE LOG clause When an error is encountered while inserting or parsing a row, the database server writes the error to the specified location.
NOTIFY TRACE EVENT statement Logs a user-defined trace event to a trace session. See NOTIFY TRACE EVENT statement.
TRY...CATCH statement You can use a BEGIN TRY...END TRY statement (with BEGIN CATCH...END CATCH) as an error handler to obtain information about errors that occur within the compound statements. See TRY statement.
The following functions and system procedures have been added to obtain information about errors. The procedures and functions can be used anywhere within a statement, not just within an error handler.
Statements that include an ENCRYPTED KEY or KEY clause can now use variable names You can specify either a string or a variable name for the ENCRYPTED KEY or KEY clause. This change affects the following statements:
![]() |
Discuss this page in DocCommentXchange.
|
Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0 |