Modeling Data Warehouse with Data Vault 2.0

What is ERD? Details of ERD Concepts:

Entities,

Relationships: Cardinality types as one to one, one to many, many to many,

Attributes: Primary Key, Foreign Key

Design an ERD model from scratch

Database design begins at a high level of abstraction and becomes increasingly more concrete and specific

What is OLTP? What is DWH? How to differentiate them? Understanding  DWH Architecture with fundamentals including ETL, Staging Area, Data Mart.

Basic data optimization with normalization and denormalization concepts.

Insert & Delete & Update Anomalies

First, second, and third normal form

Why Normalization is important for OLTP?

Why Denormalization is important for OLAP?

These methodologies are a result of research from Bill Inmon which proposes the Top-Down Approach and Ralph Kimball that offers the Bottom-Up approach.

Why Dimensional model is important? Details of Fact, Dimension, Attribute.

Comparison of Dimensional Model and 3NF

Detail description regarding to Star and Snowflake Schema

Understanding of Slowly Changing Dimensions to set up dimension tables

Why Conformed Dimensions are important?

Define ER Diagram based on sample business scenario, turn into the 3NF model and finalize with Dimensional Model

The video includes the following content :

- Today's challenges

- What is Data Vault

- Why Data Vault is significant

- Benefits & Drawbacks

Video gives comprehensive information about HUB, LINK and SATELLITE entities.

Explain the importance of many to many relationships in LINK tables.

Learn modeling steps of Data Vault and design a model from scratch

Display the behavior of target Data Vault tables (Hub, Link and Satellite) when there is an insert or update in source operational tables.

LİNK tables are used to model associations, hierarchies and transactions. How to differentiate them when modeling Data Vault.

What is transactional data? How to model them?

An alternative modeling approach for transactional data.

Detail explanation of Link to Link approache

How to handle granularity and schema changes in Data Vault structure. 

Detail explanation of Same as Link table

Detail explanation of Hierarchical Link table

Detail explanation of Exploration Link table

Describe the purpose of Load End Date column in Satellite tables.

Detail explanation of Multi-Active Satellite  table

Describe scenarios that Status Tracking Satellite is required.

Describe scenarios that Record Tracking Satellite is required.

Explain Effectivity Satellite based on Driving Key concept and describe the differences from regular Link Satellite.

The Data Vault 2.0 architecture is based on three layers: the staging area, enterprise data warehouse layer and the information layer

Implementation of Soft and Hard rules throughout the ETL processes

A Point-in-Time (PIT) table is a modified Satellite that helps to increase the query performance.

Bridge tables improve the performance on Raw Data Vault by reducing the number of required joins for the query.

Reference tables are lookup tables to store standard codes that are commonly used to describe the business keys.

Why do we need Information marts or dimensional models and how to establish them in Data Vault.

Describe how to build a Type-1 Dimension Table in Data Vault with a single Satellite.

Describe how to build Type-1 Dimension Table in Data Vault with a Multiple Satellite.

Describe how to build a Type-2 Dimension Table in Data Vault with a Single Satellite.

Describe how to build Type-2 Dimension Table in Data Vault with a Multiple Satellite.

Describe how to build a Fact Table in Data Vault.

Describe the differences between 3NF , Dimensional Model and Data Vault

Video includes practice to convert the 3NF model to Data Vault

Video includes practice to convert the Dimensional model to Data Vault

Definition of Full and Incremental Load.

Details of Incremental Load: Batch, Streaming

Describe the loading logic of HUB, LINK and Satellite Tables.