Vertica Analytics Platform Version 9.2.x Documentation
Swaps partitions between two tables.
SWAP_PARTITIONS_BETWEEN_TABLES ( '[[database.]schema.]staging‑table', 'min‑range‑value', 'max‑range‑value', '[[database.]schema.]target‑table' [, force‑split] )
Specifies a schema, by default
If you specify a database, it must be the current database.
The staging table from which to swap partitions.
|The minimum and maximum value of partition keys to swap, where min‑range‑value must be ≤ max‑range‑value. To swap one partition, min‑range‑value and max‑range‑value must be equal.|
The table to which the partitions are to be swapped. The target table cannot be the same as the staging table.
Optional Boolean argument, specifies whether to split ROS containers if the range of partition keys spans multiple containers or part of a single container:
One of the following:
- DBADMIN role
- Owner of both tables
- USAGE privileges on both schemas, and TRUNCATE and INSERT privileges on both tables.
The following attributes of both tables must be identical:
- Column definitions, including NULL/NOT NULL constraints
- Partition clause
- Number of projections
- Projection sort order
- Primary and unique key constraints. However, the key constraints do not have to be identically enabled. For more information on constraints, see Constraints in the Administrator's Guide.
If the target table has primary or unique key constraints enabled and copying or moving the partitions will insert duplicate key values into the target table, Vertica rolls back the operation.
- Check constraints. For
COPY_PARTITIONS_TO_TABLE, Vertica enforces enabled check constraints on the target table only. For
SWAP_PARTITIONS_BETWEEN_TABLES, Vertica enforces enabled check constraints on both tables. If there is a violation of an enabled check constraint, Vertica rolls back the operation.
- Number and definitions of text indices.
The following restrictions apply to the source and target tables:
- If the source and target partitions are in different storage tiers, Vertica returns a warning but the operation proceeds. The partitions remain in their existing storage tier.
- The following tables cannot be used as sources or targets:
- Temporary tables
- Virtual tables
- System tables
- External tables
SWAP_PARTITIONS_BETWEEN_TABLES returns an error if both of the following conditions are true of the staging or target table:
- The table's partition expression includes a GROUP BY clause—for example, hierarchically partitioned tables.
- The table has projections that aggregate data—for example, live aggregate or Top-K projections.
See Swapping Partitions.
Was this topic helpful?