Executor: HiRDB administrator and table owner (or user with DBA privilege)

When the amount of data in a table increases significantly because data is added repeatedly, processing performance for the table might become degraded. In such a case, it is advisable to increase the number of table row partitions.

Notes

1. In the case of a table with key range partitioning, first use DROP TABLE to delete the table, then use CREATE TABLE to redefine the table. While you are redefining the table, you can increase the number of table row partitions.
2. In a table with hash partitioning, you use ALTER TABLE to increase the number of table row partitions.
3. Increasing the number of row partitions in a table invalidates any stored routines that use that table. If this happens, use the ALTER PROCEDURE or ALTER ROUTINE statement to re-create each stored routine.
4. Increasing the number of row partitions in a table specified in a trigger SQL statement invalidates the trigger. If this happens, use the ALTER TRIGGER or ALTER ROUTINE statement to re-create the trigger.
5. After the number of table row partitions has been increased, execute the optimizing information collection utility (pdgetcst command) if necessary. Note, however, that this utility cannot be applied to an abstract data type. For details about whether execution of the optimizing information collection utility is required, see the manual HiRDB Version 9 Command Reference.

Organization of this section

13.10.1 Example 1: Increasing the number of row partitions in a table with key range partitioning

13.10.2 Example 2: Increasing the number of row partitions in a table with flexible hash partitioning

13.10.3 Example 3: Increasing the number of row partitions in a table with FIX hash partitioning