Teradata Tutorial - Indexing | Index Selection Considerations | DWHPRO
The Teradata Tutorial to support the selection of indexes How much space does the Teradata index occupy? An index can take up surprisingly much space, especially if the Teradata system does not automatically apply Block Level Compression to the index. A NUSI can then take up many times the base table's space because multivalue compression is not applied to a NUSI! On what kind of table is the index needed? Depending on the type of table, different considerations are necessary regarding how…
What Snowflake Does Better Than Teradata: Zero-Copy Clones | Is It Possible? | DWHPRO
If a zero-copy clone of a table is created, the clone uses no storage because it shared the original table's existing micro-partitions when it was cloned. Only pointers are set for the cloned table, which points to the existing table's micro partitions.
Future And Past? Snowflake Versus Teradata | Can Snowflake Meet The High Expectations?
In this article, I will explain the main differences in the Architecture between Teradata and Snowflake.
8 Teradata Access Paths You Should Know | DWHPRO
The optimizer has various access paths to choose from when creating the execution plan. Each of these access paths has certain advantages and disadvantages. In this blog post I will introduce you to the 8 most important access paths. Do not be surprised that the hash index is not included. Teradata has completely replaced the hash index by the single-table join index and recommends in the latest documentation not to use it anymore. The single table join index can do everything the hash index…
How To Speed Up Your PPI Tables With A Secondary Index | DWHPRO
As we saw in the example where we queried a Teradata PPI table using only the Primary Index, it was necessary to check each partition to see if it contained the Primary Index value we were looking for.
Teradata DIAGNOSTIC HELPSTATS ON FOR SESSION | DWHPRO
Using the command "DIAGNOSTIC HELPSTATS ON FOR SESSION" we enable an option that displays the statistics required by the optimizer at the end of each execution plan (when the EXPLAIN command is used). Below is an example: