Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.


From MIKE2.0 Methodology

Jump to: navigation, search

Teradata develops and sells a relational database management system of same name. The company differentiates itself from competitors on the basis of scalability and parallelism across data volume, breadth, number of users, and complexity of queries.

Teradata is a popular choice for large, enterprise data warehousing applications.

Teradata has added potentially their most signficant enhancement in a decade - Teradata 14 Hybrid Columnar.

The unique innovation by Teradata, in Teradata 14, is to add columnar structure to a table , effectively mixing row structure, column structures and multi-column structures directly in the DBMS which already powers over half of the large data warehouses. With intelligent exploitation of Teradata Columnar in Teradata 14, there may no longer be the need for Teradata customers to go outside the data warehouse DBMS for the power of performance that columnar provides and it is no longer necessary to sacrifice robustness and support in the DBMS that hold the post-operational data.

A major component of that robustness is parallelism, a feature that has obviously fueled much of Teradata’s leadership position in large-scale enterprise data warehousing over the years. Teradata’s parallelism, working with the columnar elements, are creating an entirely new paradigm in analytic computing - the pinpoint accuracy of I/O with column and row partition elimination. With columnar and parallelism, the I/O executes very precisely on data interesting to the query. This is finally a strong, and appropriate, architectural response to the I/O bottleneck issue analytic queries have been living with for a decade.

Many shops, with columnar databases, are carrying the same data in both row- and columnar DBMS. Given the sensitivity of the platform to the workload, this is seen as a reasonable alternative to forcing all processing into one or the other. In particular, most corporate data that is kept in columnar databases is also kept in the row-based data warehouse for the general-purpose many-column reporting that is typically done there. Teradata 14 allows the data manager to store some columns by themselves in a series of “containers” and to store other columns with other columns in other containers.

Wiki Contributors
Collapse Expand Close