Data Modeling
A collection of 20 issues
Teradata - Merging two change history tables
Have you encountered a poorly designed physical data model where object columns are distributed randomly across tables, and you wish to unify them in their rightful place?
Merging non-historical tables is simple, but the process becomes more complex when historization is applied to at least one of the tables.
Change
Real-World Map-Reduce Implementations: Design and Fault Tolerance
Enhancing Your Teradata Vantage Design with Teradata Historisation: A Comprehensive Method
Teradata Referential Integrity: What it is and Why You Need it for Data Consistency and Performance
Introduction to Teradata Referential Integrity
What is Teradata Referential Integrity?Referential integrity ensures that a value created in a foreign key (FK) column of a referencing (child) table also exists as a primary key (PK) in the referenced (parent) table. The parent table's column does not have to
7 Deadly Sins That Destroy A Teradata Data Warehouse
The Importance of Teradata Surrogate Keys
Why You Need a Performance Specialist for Your Data Warehouse Project
When do you need a fire brigade most? When your house is on fire!
When is the best time to establish the fire brigade?
No, not when your house is on fire, but before the city the house is located in is founded.
Want more practical data engineering analysis like
The Importance of a Good Data Model for Teradata Performance Optimization
Welcome to part two of our Teradata performance optimization series. In this article, we will delve into how a good data model can prevent future performance issues in data warehousing projects. We will also discuss the drawbacks of taking over operational systems' source definitions directly and th
Understanding Soft Referential Integrity and Its Role in Improving Performance
Learn about referential integrity and how it ensures data consistency in databases. Discover soft referential integrity and its use in inner join elimination.