# Data Warehouse Info > A vendor-neutral practitioner's reference for analytical data warehousing: the patterns, techniques, and trade-offs of building and operating data warehouses, written for working data engineers and architects. This file is a curated, machine-readable index of the publication for AI agents and developer tooling. Each link points to a full article; the site is the canonical source. The publication is editorially independent and vendor-neutral. ## Foundations - [What is a data warehouse?](https://datawarehouseinfo.com/data-warehouse/): A data warehouse is a centralized repository for integrated, historical analytical data. This guide covers architecture, dimensional modeling, ETL vs ELT, cloud platforms, and the trade-offs that determine when a warehouse is the right tool. - [Building a warehouse with coding agents](https://datawarehouseinfo.com/foundations/agentic-warehousing/): Agentic data engineering: building a warehouse with AI coding agents across the whole lifecycle. Where agents earn their keep, where they fail silently, and the governance the speed demands. - [Data vault modeling](https://datawarehouseinfo.com/foundations/data-vault-modeling/): Data vault modeling organizes warehouse data into hubs, links, and satellites for auditability, source traceability, and resilience to schema changes. This guide covers the core structures, Data Vault 2.0 additions, the mart layer requirement, and when data vault is the right choice. - [Data warehouse automation](https://datawarehouseinfo.com/foundations/warehouse-automation/): Data warehouse automation tools reduce the hand-coded work of building and maintaining warehouse pipelines by deriving load logic from metadata, models, or templates. This guide covers the spectrum of automation approaches, what model-driven tools do, the trade-offs, and when data warehouse automation earns its cost. - [Data warehouse loading and operations](https://datawarehouseinfo.com/foundations/warehouse-loading-and-operations/): How a data warehouse stays current: full vs incremental loading, change data capture, watermarks, load ordering, idempotency and recovery, late-arriving data, and the monitoring that keeps it reliable. - [Dimensional modeling: a practitioner's guide](https://datawarehouseinfo.com/foundations/dimensional-modeling/): A practitioner's guide to dimensional modeling: star schemas, fact and dimension tables, grain, surrogate keys, SCD strategies, and where the model breaks down at scale. - [Modern warehouse platforms](https://datawarehouseinfo.com/foundations/modern-warehouse-platforms/): Snowflake, BigQuery, Redshift, and Databricks each make different architectural trade-offs. This guide covers what distinguishes them, how their cost models behave under different workload patterns, and the selection criteria that actually matter when choosing a platform. ## Practice - [Advanced dimensional modeling: bridge tables and the hard cases](https://datawarehouseinfo.com/practice/advanced-dimensional-modeling/): Advanced dimensional modeling beyond the basics: bridge tables, multivalued and inferred-member dimensions, comment dimensions, and multi-timezone facts. - [Automating data vault generation](https://datawarehouseinfo.com/practice/automating-data-vault-generation/): Why data vault is the most automatable warehouse methodology, what metadata-driven generation produces, what stays human, and when generation earns adoption. - [Building a data warehouse: a four-phase playbook](https://datawarehouseinfo.com/practice/building-a-data-warehouse/): How a data warehouse project actually gets built, across discovery, design, development, and deployment, with the Kimball vs Inmon choice treated as a concrete decision, not a debate. - [Change data capture: implementation strategies](https://datawarehouseinfo.com/practice/change-data-capture/): How log-based, timestamp-based, and trigger-based CDC work in production: the snapshot-to-streaming handoff, schema-evolution failure modes, and the disciplines that keep pipelines correct. - [Data cleansing in the warehouse: where it belongs](https://datawarehouseinfo.com/practice/data-cleansing/): Where data cleansing sits in a modern warehouse load: the staging-to-curated boundary, the rule categories that catch real defects, the test-at-the-transform-layer pattern, and the observability that catches the drift the rules miss. - [Data extraction models: full, incremental, and log-based CDC](https://datawarehouseinfo.com/practice/data-extraction-models/): The seven data extraction patterns a warehouse encounters in practice, what each one assumes about the source, where each one fails, and how the modern connector stack (Fivetran, Airbyte, Estuary, Debezium, Kafka) decides between them. - [Data integration: approaches and when to use each](https://datawarehouseinfo.com/practice/data-integration/): Data integration approaches compared: ETL, ELT, CDC, replication, virtualization, and streaming, and the trade-offs that pick the winner for each source. - [Data masking in the data warehouse](https://datawarehouseinfo.com/practice/data-masking/): How static, dynamic, and on-the-fly data masking actually work in a cloud warehouse, including the mask-before-load versus mask-in-warehouse axis, column-level masking policies on Snowflake, BigQuery, and Databricks, and the trade-offs between tokenization, encryption, and hashing under GDPR, CCPA, and HIPAA. - [Data modeling phases: conceptual, logical, and physical](https://datawarehouseinfo.com/practice/data-modeling-phases/): Data modeling phases explained: what the conceptual, logical, and physical models each deliver, where dbt and data contracts fit, and the handoffs that decide if the model holds. - [Data virtualization: federated query in modern stacks](https://datawarehouseinfo.com/practice/data-virtualization/): How data virtualization works as a technique, what it shares with and how it differs from federated query and the logical data warehouse, where it fits in cloud warehouse stacks, and the failure modes that determine when virtualization holds up in production. - [Data warehouse governance that survives contact with delivery](https://datawarehouseinfo.com/practice/data-warehouse-governance/): Governance for the warehouse specifically: who owns definitions, access and audit mechanics, change management for shared schemas, and why programs fail. - [Data warehouse metadata: catalogs, lineage, and repositories](https://datawarehouseinfo.com/practice/data-warehouse-metadata/): How technical, business, and operational metadata get organized in a modern warehouse stack, including the shift from monolithic metadata repositories to federated data catalogs, dbt-driven lineage, and OpenLineage as the cross-tool standard. - [Data warehouse testing: validation, regression, and performance](https://datawarehouseinfo.com/practice/data-warehouse-testing/): What to test in a production warehouse pipeline, where each kind of test lives, and how dbt tests, Great Expectations, and contract patterns fit together without producing a green dashboard over wrong data. - [Logical data warehouse: the architectural pattern](https://datawarehouseinfo.com/practice/logical-data-warehouse/): The logical data warehouse unifies a physical warehouse with lakehouses, operational stores, and SaaS sources behind a single query layer. How the pattern actually works in 2026, where it fits, and where it quietly breaks. - [Normalization and denormalization in data warehousing](https://datawarehouseinfo.com/practice/normalization-and-denormalization/): Normalization vs denormalization for analytical workloads: where 3NF still belongs in a 2026 warehouse, why columnar engines have made denormalization the default for query layers, and how to think about the trade-off layer by layer. - [Slowly changing dimensions: implementation strategies](https://datawarehouseinfo.com/practice/slowly-changing-dimensions/): How SCD Type 1, 2, 3, and the hybrid types actually work in a production warehouse, including active row identification, fact loading under Type 2, and the edge cases that bite teams in practice. - [Surrogate key management: generation, lookup, and pitfalls](https://datawarehouseinfo.com/practice/surrogate-key-management/): How to generate and manage surrogate keys in a 2026 cloud warehouse: integer sequences, hash-based deterministic keys, UUID v7, the fact-loading lookup under Type 2 SCD, and the edge cases that produce silent errors. - [The business case for data warehouse automation](https://datawarehouseinfo.com/practice/warehouse-automation-business-case/): What the benefits of data warehouse automation actually are, the mechanism behind each, the costs the case must carry, and when it holds or collapses. - [The enterprise data warehouse: what the E actually means](https://datawarehouseinfo.com/practice/enterprise-data-warehouse/): What makes a warehouse an enterprise data warehouse: the integration commitment, the two classical EDW architectures, and whether the term still matters. - [Where coding agents quietly get the warehouse wrong](https://datawarehouseinfo.com/practice/where-agents-fail-warehouse-sql/): AI-generated SQL that parses, runs, and passes your tests but answers the wrong question: the silent failure modes of coding agents in the warehouse, and what actually catches them. ## Architecture - [Data warehouse automation vs AI coding agents: where the logic lives](https://datawarehouseinfo.com/architecture/automation-vs-agentic-engineering/): Data warehouse automation vs AI coding agents: a build-vs-buy framework for your data stack, by scale, correctness stakes, and who owns the warehouse logic. - [Data warehouse vs data lake vs data mart vs lakehouse](https://datawarehouseinfo.com/architecture/data-warehouse-vs-mart-vs-lake/): Data warehouse vs data lake vs data mart vs lakehouse: four distinct architectural commitments, what each one actually is, how they compare on storage, governance, query engine, and workload, and when each is the right choice in a 2026 stack. - [ETL vs ELT](https://datawarehouseinfo.com/architecture/etl-vs-elt/): ETL vs ELT: what the order of operations actually changes, why cloud columnar warehouses shifted the default from ETL to ELT, the trade-offs that determine which pattern fits a given workload, and a note on where reverse ETL fits. - [How to choose a data warehouse platform](https://datawarehouseinfo.com/architecture/choosing-a-warehouse-platform/): A decision framework for choosing a data warehouse platform: billing shape vs workload shape, ecosystem gravity, open-format posture, and exit economics. - [How to evaluate data warehouse automation tools](https://datawarehouseinfo.com/architecture/evaluating-warehouse-automation-tools/): A practitioner's framework for evaluating data warehouse automation tools: six axes that matter, the questions that expose weak fits, and worked examples. - [Lakehouse vs data warehouse: the honest 2026 state](https://datawarehouseinfo.com/architecture/lakehouse-vs-warehouse/): Lakehouse vs data warehouse in 2026: what the lakehouse is, how open table formats collapsed the storage distinction, and where each side still wins. - [OLTP vs OLAP: which workload goes where](https://datawarehouseinfo.com/architecture/oltp-vs-olap/): OLTP vs OLAP: what each is optimized for, how HTAP and columnar cloud warehouses blurred the line, and which side a given workload actually belongs on. - [Referential integrity in a data warehouse](https://datawarehouseinfo.com/architecture/referential-integrity/): Referential integrity in a data warehouse is a decision, not a default. A framework for choosing between database-enforced foreign keys, informational constraints, ELT-layer assertions, and unenforced declarations on Snowflake, BigQuery, Redshift, Databricks, and lakehouse table formats. - [Star schema vs snowflake schema](https://datawarehouseinfo.com/architecture/star-schema-vs-snowflake-schema/): Star schema vs snowflake schema: when to denormalize the whole dimensional model, when to keep hierarchies normalized, and what changes on modern columnar warehouses where the textbook trade-offs no longer hold. ## Glossary - [Glossary](https://datawarehouseinfo.com/glossary/): 39 definitions of the working vocabulary, each linking to the article where the term is developed in depth. ## Courses - [Data Warehouse Fundamentals](https://datawarehouseinfo.com/courses/data-warehouse-fundamentals/): A six-lesson on-ramp to analytical data warehousing: what a warehouse is, how it's modeled, how it's loaded, and where it runs.