On an existing table with hash-range partitioning, you can add
additional range subpartitions. You cannot add Hash-range partitioning to an existing
unpartitioned table.
Prerequisites
Database Version |
Table Partition Privileges |
SAP Sybase IQ 15.3 and 15.4 |
You must have one of:- DBA authority
- SPACE ADMIN authority, along with one of:
- ALTER permission on the table
- You own the table
|
SAP Sybase IQ
16.0 |
You must have one of: - ALTER ANY OBJECT system privilege
- CREATE permission on the dbspace along with
one of:
- ALTER ANY TABLE system
privilege
- ALTER permission on the table
- You own the table
|
-
The SAP Sybase IQ resource is authenticated and
running.
-
In a multiplex
configuration, the coordinator node is running.
-
You must be licensed for the Very Large Database
Management option (IQ_VLDBMGMT).
- The table is already hash-range partitioned and resides in the IQ
main store.
Task- In the Perspective Resources view, select the resource, and
select .
- In the left pane, expand , and then select
Tables.
- Select a table with hash-range partitioning from the right pane and either:
- Click the arrow to the right of the name and select
Properties, or
- From the Administration Console menu bar, select .
The Table Properties view appears.
- Select Partitions.
- Click New.
The Create Partition Wizard appears.
- On the Partition Type, Partition Key, and Subpartition key pages, click
Next. These values cannot be changed on a table that is
already hash-range partitioned.
- On the Subpartitions page, click Add. The Define a Partition
view appears. Specify:
- Name – enter a descriptive name for the partition.
- Constraint – (read only) less than or equal (<=) is the only constraint currently
supported.
- Value – enter a value for the upper boundary of the partition. The value must be
appropriate for the data type of the partition key.
- Dbspace – select the dbspace for the partition from the drop-down.
Click OK. Repeat this step to add
additional partitions.
Note:
-
When adding multiple partitions to a table, the
constraint value of each successive partition must be greater than that of the previous
partition. For example, if the constraint value of the first partition is 100, the
constraint value of the next partition must be 101 or higher.
-
If an invalid constraint value is specified, no error
message appears when you click OK on the Define a Partition
dialog, but does appear when you click OK or
Apply to complete the partitioning process.
- Click Next.
- (Optional) On the Columns page, if you want to
store the data for any individual columns in separate dbspaces from the
partition, click Add. Choose the column, partition, and
dbspace from each drop-down list, and click OK. Repeat
this step to specify additional columns to be stored separately from the
dbspaces of their respective partitions.
- Click Finish to return to the Table Properties Partitions
page.
- Do one of:
- Click OK to update any changes to the
database and exit the properties view.
- Click Apply to update any changes to the database, but
remain in the properties view.
- Click Cancel to cancel any changes not
updated to the database and exit the properties view.
Note: If an error is detected with a constraint
(partition bound) value, an error message appears.
Highlight the invalid partition and do one
of:- Click Edit, correct the value, and click
OK.
- Click Delete to remove the invalid partition.
Click Apply or
OK to complete the partitioning process.