Unless otherwise noted, see Chapter 1, “SQL Statements,” in Reference: Statements and Options for syntax and examples.
The following statements are new or changed in Sybase IQ 15.0:
ALTER DBSPACE statement
ALTER DBSPACE supports configurable tablespaces and partitioning. Operations that can be performed on dbfiles include add, drop, rename logical name, and rename the file path. See “Naming dbspaces”.
ALTER FUNCTION statement
New ALTER FUNCTION syntax supports the sa_dependent_views procedure.
ALTER INDEX statement
ALTER INDEX statement supports configurable tablespaces and partitioning.
ALTER LOGIN POLICY statement
New syntax supports login policies described in “Login management changes”.
ALTER MULTIPLEX RENAME statement
The ALTER MULTIPLEX RENAME and ALTER MULTIPLEX SERVER statements support multiplex configuration outside of Sybase Central. For syntax and examples, see ALTER MULTIPLEX RENAME statement in Appendix A, “Multiplex Reference,” in Using Sybase IQ Multiplex.
ALTER MULTIPLEX SERVER statement
For syntax and examples, see ALTER MULTIPLEX SERVER statement in Appendix A, “Multiplex Reference,” in Using Sybase IQ Multiplex.
ALTER TABLE statement
ALTER TABLE statement supports configurable tablespaces and partitioning.
ALTER USER statement
ALTER USER statement supports login management. See “Login management changes”.
ALTER VIEW statement
New ALTER VIEW syntax supports the sa_dependent_views procedure.
BACKUP statement
There are four significant changes to backup and restore:
An IQ full, incremental-since-full or incremental backup may be restricted to only the set of read-write files in the database using the READWRITE FILES ONLY keywords. The read-write files must be IQ dbspaces. For syntax and details, see “BACKUP statement” in Chapter 1, “SQL Statements,” in Reference: Statements and Options
An IQ backup may back up a set of read-only dbspaces and/or read-only files. The read-only dbspaces/files must be IQ dbspaces.
A restore of a backup may, optionally, restore only a subset of the dbspaces and/or files. The subset must be READONLY dbspaces and/or files. For syntax, see “RESTORE statement” in Chapter 1, “SQL Statements,” in Reference: Statements and Options.
System tables now contain backup history. See “SYSIQBACKUPHISTORY system view” and “SYSIQBACKUPHISTORYDETAIL system view” in Chapter 8, “System Views,” of Reference: Building Blocks, Tables, and Procedures.
COMMENT statement
The COMMENT statement now supports:
Tablespaces and partitioning described in “Information lifecycle management”.
The clause LOGIN POLICY policy-name. See “Login management changes”
The clause KERBEROS LOGIN "client-Kerberos-principal".
CREATE DATABASE statement
The CREATE DATABASE statement now supports:
Range partitioning and tablespace management. See “Sizing guidelines for main and temporary stores”.
Database collation improvements. See “Database collation improvements”
Message log archiving. See “Message log archiving”.
Encryption enhancements. See “CREATE DATABASE ENCRYPTED clause extension”.
Changes to identifiers such as table, user, dbspace and database names. See “Changes to identifiers”.
CREATE DBSPACE statement
The CREATE DBSPACE statement now supports:
Range partitioning and tablespace management. See “Dbspace attributes and operations”.
Rollback instead of waiting when a server is out of space. See “Out of dbspace handling”.
Using IQ local store for store type in the CREATE DBSPACE command is deprecated.
CREATE FUNCTION statement
A new stored procedure, sa_dependent_views, provides information about dependent views for a table or view. Modifications to the ALTER VIEW, ALTER FUNCTION, and CREATE FUNCTION SQL statements support the new procedure. For syntax and examples, see CREATE FUNCTION statement in Chapter 1, “SQL Statements,” in Reference: Statements and Options.
CREATE INDEX statement
CREATE INDEX syntax is unchanged for this release. If you omit the IN clause, which signals index placement, Sybase IQ creates the index in the dbspace where the table is created. You must have DBA authority or RESOURCE authority and CREATE privilege in the specified dbspace to create an index.
Sybase IQ has significantly improved the performance of loading High_Group (HG) indexes and Containment (also called WORD) (WD) indexes, while transactions are still allowed to access the tables being loaded. This load performance improvement for HG and WD indexes affects CREATE INDEX.
CREATE JOIN INDEX statement
CREATE JOIN INDEX now supports:
Range partitions and configurable tablespaces
Read-only and read-write dbspaces and files.
CREATE LOGIN POLICY statement
New syntax supports login policies described in “Login management changes”.
CREATE MULTIPLEX SERVER statement
You can now configure your multiplex manually using DDL statements for creating, altering and dropping multiplex server definitions. See Chapter 2, “Managing Multiplex Servers,” and Appendix A, “Multiplex Reference,” in Using Sybase IQ Multiplex.
CREATE TABLE statement
CREATE TABLE now supports range partitions and configurable tablespaces. See “Object placement for non-partitioned tables” and “Object placement for partitioned tables”.
CREATE USER statement
New syntax supports login policies described in “Login management changes”.
DROP DBSPACE statement
New syntax supports operations described in “Dbspace attributes and operations”
DROP LOGIN POLICYstatement
New syntax supports login policies described in “Login management changes”.
DROP MULTIPLEX SERVER statement
You can now configure your multiplex manually using DDL statements for creating, altering and dropping multiplex server definitions. See Chapter 2, “Managing Multiplex Servers,” and Appendix A, “Multiplex Reference,” in Using Sybase IQ Multiplex.
DROP USER statement
New syntax supports login policies described in “Login management changes”.
GRANT statement
New syntax supports login policies described in “Login management changes”and configurable tablespaces and partitioning described in “Read-only and read-write dbspaces and files”.
LOAD TABLE statement
The LOAD TABLE syntax includes the new STRIP clause keyword RTRIM. The keyword RTRIM replaces the keyword ON, which has been deprecated.
When bulk loading large objects, the USING CLIENT FILE clause applies to both primary and secondary files. (If you have the Large Objects Management Option, see Large Objects Management in Sybase IQ for details.)
RESTORE statement (see BACKUP statement)
REVOKE statement
See GRANT statement.
TRUNCATE TABLE statement
The partition clause specifies which partition to truncate. It does not affect data in other partitions.