Rules for Using Client Archive and Load Utilities With A Column-Partitioned Table - Advanced SQL Engine - Teradata Database

SQL Data Definition Language Detailed Topics

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-24
dita:mapPath
jpx1556733107962.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1184
lifecycle
previous
Product Category
Teradata Vantage™
  • You cannot load rows into a column-partitioned table using the MultiLoad or FastLoad utilities.
  • You can load rows into a column-partitioned table using Teradata Parallel Data Pump array INSERT operations.

    You can also use INSERT … SELECT statements to load rows from a source table into a column-partitioned target table. The source can be a primary-indexed table, a column-partitioned table, or an nonpartitioned NoPI table.

    For more information about using the Teradata Parallel Data Pump utility to load rows into a column-partitioned table, see Teradata® Parallel Data Pump Reference, B035-3021 and Teradata Vantage™ - Database Design, B035-1094.

  • The following rules apply to using the Archive/Recovery utility with column-partitioned tables.
    • You can archive, restore, and copy a column-partitioned table with column partitioning or row partitioning or both.

      You can also archive, restore, and copy databases or users that contain column-partitioned tables.

    • You cannot archive, restore, or copy selected partitions of a column-partitioned table.
    • You should not archive, restore, or copy selected partitions of a column-partitioned table.

      This is valid for 2-byte partitioning, but it is a deprecated feature.

      You cannot archive, restore, or copy selected partitions of an column-partitioned table with 8-byte partitioning.