Some restrictions apply to table partitions.
Partition keys cannot contain:
Partition key columns can contain NULL and DEFAULT values. All NULL values are mapped to the same partition.
You can have up to 8 partitioning key columns for hash partitions and only one key column for range partitions or subpartitions.
You can define up to 1024 range partitions or subpartitions.
You can perform DML operations including LOAD, INSERT, DELETE, TRUNCATE, and TRUNCATE TABLE PARTITION. UPDATE of partition key columns is not supported and results in an error. You can perform the UPDATE of all other columns of a partitioned table.
SAP Sybase IQ generates an exception for DML operations on a READ-ONLY table or READ-ONLY table partition. INSERT and LOAD statements or INSERT by updatable cursor generate an error and operations roll back, if the given row does not fit into the specified range of partitions.
Operation | Restriction |
---|---|
Drop | You cannot drop a column from a partition key or range subpartition key. You cannot drop the last partition of a partitioned table. |
Partition an unpartitioned table | An existing table cannot be made hash partitioned. |
Merge two adjacent partitions | Both partitions must reside in the same dbspace. No data movement is required. |
Split a partition | All rows must belong
to the first of the two partitions after splitting. Split
partition must be on same dbspace as original so that no data
movement is required. You can split a range subpartition only if no data must be moved. All existing rows of the subpartition to be split must remain in the first subpartition after the split. |
Move a partition to a new dbspace. | All rows of the partition are moved to data pages in the new dbspace. CREATE permission in the new dbspace is required. |