Syntax changes for SAP Sybase IQ 16.0 SP2.
| Statement | Description |
|---|---|
| ALTER AGENT |
New statement to change the agent port, or agent user name and password for the SCC agent on the target server. You can now use the SCC agent to enable high availability for a multiplex. See ALTER AGENT Statement in Reference: Statements and Options. |
| ALTER LS POLICY |
New root logical server policy option ENABLE_AUTOMATIC_FAILOVER, which defaults to OFF. See ALTER LS POLICY Statement in Reference: Statements and Options. |
| CREATE AGENT |
New statement to specify agent port, agent user name, and password for the SCC agent on the target server. You can now use the SCC agent to enable high availability for a multiplex. See CREATE AGENT Statement in Reference: Statements and Options. |
| CREATE DBSPACE |
New IQ CACHE STORE keyword for creating a cache dbspace. See CREATE DBSPACE Statement in Reference: Statements and Options. |
| CREATE LS POLICY |
New root logical server policy option ENABLE_AUTOMATIC_FAILOVER, which defaults to OFF. See CREATE LS POLICY Statement in Reference: Statements and Options. |
| DROP AGENT |
New statement to drop the SCC agent from the target server. You can now use the SCC agent to enable high availability for a multiplex. See DROP AGENT Statement in Reference: Statements and Options. |
| LOAD TABLE | The FROM clause now supports compressed client and server files only in gzip format. Any file with an extension ".gz" or ".gzip" is assumed to be a compressed file. |
|
In releases earlier than 16.0 SP2, SAP Sybase IQ silently truncated the results when converting from TINYINT, SMALLINT, INT, DOUBLE, DATE, DATETIME, TIME, BIGINT, UNSIGNED BIGINT, or UNSIGNED INT to CHAR or VARCHAR. If a problem occurs when converting these data types in 16.0 SP2, SAP Sybase IQ logs the failure as an error or warning in the .iqmsg file. If the CONVERSION_ERROR option is ON, SAP Sybase IQ reports the problem as an error. If the CONVERSION_ERROR option is OFF, the problem is reported as a warning. |
|
| SELECT |
SELECT now supports the FIRST, TOP, and LIMIT row limitation
clauses in the top query block in a
statement:
FIRST | TOP { ALL | limit-expression } [ START AT startat-expression ]
LIMIT { [ offset-expression, ] limit-expression
| limit-expression OFFSET offset-expression }
See SELECT Statement in Reference: Statements and Options. |