SAP Sybase IQ supports fully parallel bulk loads for range-, hash-, and hash-range partitioned tables.
Load performance for the same volume of data may vary depending on the type of the table being loaded. Unpartitioned tables load more quickly than partitioned tables. Range-partitioned tables load more quickly than hash- or hash-range partitioned tables. Loading data into a single range partition should be comparable to loading into an unpartitioned table. The load speed depends on a number of factors, including but not limited to the number of cores, bandwidth of the underlying I/O system, and amount of physical memory.
Load performance of partitioned tables also depends on partition-key data characteristics. Range-partitioned tables get best load performance when partition key data is grouped in partition order. Hash- and hash-range partitioned tables achieve best load performance when partition key data has uniform value distribution.
The following applies to loading into a range-partitioned table or a hash-range partitioned table and the range-partitioning key column or the range subpartitioning key column:
When you load data into a partitioned table, you can achieve the best performance when the partitioning column is placed first in the column list of the command. For a LOAD statement, list the partitioning columns before any other columns including large object (LOB) columns in the load file. If possible, use a preload process to rearrange data in the primary file. Similarly for an INSERT...LOCATION statement, list the partitioning columns before any other columns including large object (LOB) columns in the SELECT statement clause.
"Updating partition key column on a partitioned table is not allowed." (SQLCODE -1009417L, SQLSTATE QCB15, Sybase error code 21055)