You can partition tables or join indexes on their rows and their columns. Column partitioning enables Teradata Columnar.
Column partitioning is a physical database design choice that is not suitable for all workloads. For example, column partitioning is typically not suitable for workloads that frequently select a large number of rows and project a large number of columns from a table. However, column partitioning may be suitable if a request selects a large number of rows but projects a small number of columns, or conversely.
Column partitioning can be suitable when a small number of rows are selected and a small number columns are projected. See Column Partitioning for more information about how table and join indexes can be partitioned on their columns and how column-partitioned tables and join indexes can be applied optimally.
A column-partitioned table or join index can also have 1 or more row partitioning levels.