Natural Key
A customer number or SKU identifies a record in its source system. It is essential for tracing data back, and unreliable as the only key a warehouse joins on.
-
-
Conformed Dimension
Orders, shipments, and returns can be compared by customer or month only if those attributes mean exactly the same thing in each. That is a conformed dimension.
-
Synapse SQL Pools
A dedicated SQL pool reserves warehouse compute you pay for while it runs; a serverless pool charges for the data each query processes. They fit different jobs.
-
Warehouse, Lake, and Lakehouse
Three architectures, three different assumptions about schema, cost, and who the user is. See what each solved, what it deferred, and why the names now mislead.
-
BigQuery Architecture and Cost
BigQuery bills what a query reads or the slots it occupies. Work through column, partition, and clustering effects, dry runs, slot time, and the on-demand versus capacity choice.
-
Dimensional Modeling and Historical Restatement
A customer moves region, a sale arrives late, and a correction shows the move happened earlier. This post shows how a dimensional model attributes facts, restates history on purpose, and proves the totals still agree.
-
Warehouse Workload Isolation and Concurrency
When dashboards wait behind an export, resizing may not help. Learn how compute separation, queues, workload classes, and access controls shape warehouse performance.
-
External Tables and the Lake/Warehouse Boundary
An external table exposes files to SQL. Learn when to load a managed copy and how registration, updates, and snapshots affect correctness.
-
Designing End-to-End Data Architecture
How consumer requirements determine data contracts, logical layers, physical deployment, consistency boundaries, and recovery decisions.
-
Data Warehouse
Learn why warehouses organize data for analysis and how their role differs from operational databases and lakes.