Data warehouse
Centralized repository of structured historical data from multiple sources, optimized for analytical queries rather than transactional processing; typically uses column-oriented storage
As defined in Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
Other definitions
A specialized type of database designed specifically for analytics and business intelligence, optimized for running complex analytical queries across large datasets rather than for transactional processing.
The Marketing Expert: Sell Anything with this Trick | April DunfordA centralized, structured database optimized for analysis, used to combine many data sources for reporting and scoring.
Henry Schuck - Building ZoomInfo - [Invest Like the Best, EP.330]
Where it comes up · 7
- Databricks: From Data to Decisions5 claims
- Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker5 claims
- Next-Level Financial Modeling with AI and Automation for CFOs with Chase Wright2 claims
- Peter Reinhardt - Learning How to Sell – [Founder’s Field Guide, EP. 34]2 claims
- Ali Ghodsi – The Past, Present, and Future of Big Data – [Founder’s Field Guide, EP.18]1 claim
- Martin Casado - The Past, Present, and Future of Digital Infrastructure - [Invest Like the Best, EP.280]1 claim
- The Marketing Expert: Sell Anything with this Trick | April Dunford1 claim
Most important claims · 10 of 17Search all claims for “Data warehouse” →
- Snowflake was the next-generation cloud version of an existing data warehouse market, whereas Databricks' data lake market had never been well established because of inadequate technology.Databricks: From Data to Decisions
- Cloud data warehouses made it cheap enough to store all of an organization's data, so data becomes a resource firms repeatedly return to, rather than something processed once because storage was expensive, replacing costly on-premise systems like Teradata.Martin Casado - The Past, Present, and Future of Digital Infrastructure - [Invest Like the Best, EP.280]
- Equals solves the startup data problem by integrating directly with modern data infrastructure tools (Stripe, Salesforce, QuickBooks via Fivetran/Stitch-like ETL) and connecting that data into a spreadsheet interface, eliminating the need for a separate data warehouse or BI toolNext-Level Financial Modeling with AI and Automation for CFOs with Chase Wright
- Enterprises commonly use Databricks first to process data and then store it in Snowflake, because Snowflake has moved upstream into data processing while Databricks has moved downstream into data warehousing, so the two tools increasingly overlap but often coexist.Databricks: From Data to Decisions
- When you want to talk to multiple structured databases simultaneously (e.g., a data warehouse and a CRM system), doing structured data joins using an LLM is a bad idea, and you're much better off leaving data in tables and doing joins in SQL.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
- Early-stage startups face a fundamental data infrastructure problem: they lack data warehouses, BI tools, and integrated data pipelines, making it impossible to pull source system data (billing, CRM, accounting) into analysis without manual copy-paste workflowsNext-Level Financial Modeling with AI and Automation for CFOs with Chase Wright
- The most exciting future development is the lakehouse paradigm, merging data lakes used for AI with data warehouses used for data management into one platform, which would give enterprises the end-to-end capabilities that Silicon Valley tech companies had in the early 2000s.Ali Ghodsi – The Past, Present, and Future of Big Data – [Founder’s Field Guide, EP.18]
- In 2004, Stonebraker was working on an academic project that became StreamBase (a stream processing engine) and had ideas for column stores for data warehouses (popularized by Vertica), which were wildly different implementations that bore no resemblance to row stores.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
- PostgreSQL is optimal for low-end use cases (small databases, modest workloads) but not competitive for large data warehouses because it lacks column store capabilities and multi-node support, which are table stakes for scaling to terabyte-scale data.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
- Large language models score 0% accuracy on real-world data warehouse text-to-SQL tasks despite 85% accuracy on public benchmarks (Spider, BIRD) because real data contains domain-specific idiosyncratic data not present in training data, has schema complexity (100+ lines of SQL vs. 10-20 lines) and messy naming conventions (underscores, non-mnemonic column names) that public benchmarks lack.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker