From e7195f6cd92337e78aa517ba81b6fdbaf2d66489 Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Tue, 7 Jan 2025 23:11:48 -0600 Subject: [PATCH] in progress --- 0_Azure/2_AzureAnalytics/0_Fabric/demos/5_Tableau2Fabric.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/0_Azure/2_AzureAnalytics/0_Fabric/demos/5_Tableau2Fabric.md b/0_Azure/2_AzureAnalytics/0_Fabric/demos/5_Tableau2Fabric.md index 77303b41..a9294a3f 100644 --- a/0_Azure/2_AzureAnalytics/0_Fabric/demos/5_Tableau2Fabric.md +++ b/0_Azure/2_AzureAnalytics/0_Fabric/demos/5_Tableau2Fabric.md @@ -350,6 +350,10 @@ SWITCH(, , , , , ..., ) Star Schemas are a way to organize your data, where there is one fact table that contains the transactional data, and smaller dimension tables that contain characteristics. The fact table and dimension tables are connected through one-to-many relationships via unique keys. This approach helps avoid data duplication by storing only the key in your fact table. +> The diagram illustrates the relationships between a central fact table ("Sales") and its surrounding dimension tables ("Product," "Sales Territory," "Employee," "Reseller," and "Date"). + +image + #### Key Components of a Star Schema 1. **Fact Table**: