What is the best data warehouse in 2026?

BigQuery is Google Cloud's warehouse, and it has no cluster to start or size to pick. You load tables, write SQL, and Google spreads the work. On-demand, you pay $6.25 per TiB scanned after a free TiB each month. Active storage runs about $0.023 per GiB-month and drops to about $0.016 for tables untouched for 90 days. The first 10 GiB are free.

For a small dataset nothing beats it: 100 GB queried sensibly costs a few dollars a month. If you run GA4, the native export lands right in BigQuery.

The trap is well known and it hurts. BigQuery bills the columns it reads, not the rows it returns. A SELECT * reads the whole table, and LIMIT 10 doesn't lower the bill. Worse, there's no spending cap by default. One academic posted on a public forum about a roughly $14,000 charge in two hours: a Python script had scanned around 2.5 PB, and no client library showed an estimate first. On Google's developer forum, another team traced a billing spike to just three users.

The fix takes three settings: per-user and per-project quotas, maximum_bytes_billed on your jobs, and tables partitioned by date. Once usage is steady, capacity pricing (Enterprise at $0.06 per slot-hour, per-second billing with a one-minute minimum) makes the bill predictable.

Snowflake is the reference cloud data warehouse. It runs on AWS, Azure and Google Cloud and separates storage from compute: you spin up "virtual warehouses" (compute clusters) of different sizes for each workload, all reading the same data.

You pay in credits. An X-Small warehouse burns 1 credit an hour, Small 2, Medium 4: every size up doubles the cost. In AWS US East, a Standard credit costs $2.00, Enterprise $3.00 and Business Critical $4.00. Storage runs $23 per TB-month. Billing is per second, but with a 60-second minimum every time a warehouse resumes.

The main trap is auto-suspend, the idle time before a warehouse shuts down. A junior engineer posted on r/dataengineering that most of his company's warehouses were set to 10 minutes. Dropping them to 1 minute roughly halved daily credit use. The replies pushed back with a fair point: too short and you lose the cache, so analysts wait. One manager on another platform cut it to 5 minutes and long jobs started timing out on cold starts; he rolled it back. Measure before you roll it out everywhere.

Two more things to watch. Multi-cluster warehouses, which add clusters when too many users query at once, bill per cluster. And when the 30-day trial ends without a paid plan, the account is suspended: export anything you want to keep.

Databricks grew out of Spark and machine learning on large files. Databricks SQL adds a SQL warehouse that reads lakehouse tables directly. The point: one copy of the data for engineering, ML and BI.

Pricing is in DBUs (Databricks Units). We only publish the rates we could read on an official source, and that's Azure Databricks in the France Central region, Premium tier: SQL Classic $0.22 per DBU-hour, SQL Pro $0.72, Serverless SQL $0.91. AWS and Google Cloud rates differ, and the US rates we found were only on third-party sites, so check the pricing page for your own cloud and region.

Watch the double bill. On Classic and Pro you pay DBUs and your cloud's virtual machines. Only Serverless SQL bundles the compute into one price. It's the most common confusion for newcomers: the DBU rate isn't the whole story, and how many DBUs an hour you burn depends on the warehouse size you pick.

On auto-stop, field reports match Snowflake's with one nuance: some teams keep at least 5 minutes of idle time on warehouses used by humans, so analysts don't wait for a restart on every click.

ClickHouse is an open-source columnar database famous for fast aggregations. ClickHouse Cloud is the managed version run by the vendor, billed on usage with no monthly minimum.

Three tiers: Basic (up to 1 TB, single zone), Scale (unlimited storage, multiple zones, compute-compute separation) and Enterprise (SAML SSO, customer-managed keys, HIPAA and PCI). The per-unit rates we read were for European regions: an Enterprise unit (8 GiB of memory, 2 vCPU) runs $0.36027 an hour on GCP in the Netherlands and $0.46974 on AWS in Frankfurt. Pick your US region in the pricing calculator for your exact rate.

The founder of an open-source analytics product wrote up two years on ClickHouse: dashboards in milliseconds where Postgres was struggling. Also heavy joins that eat memory, limited updates and deletes, and small inserts you have to batch. Self-hosting it was, in his words, a full-time job, and on the cloud the bill can sting as volume grows. A Hacker News thread says the same about big joins, with others pointing out recent join-ordering improvements. It's still not the warehouse for models with dozens of related tables.

Redshift is AWS's warehouse. The Serverless version skips node sizing: you set a base capacity in RPUs (Redshift Processing Units) and AWS scales from there. In US East an RPU-hour costs $0.375. The minimum base is 4 RPU (64 GB of memory), which AWS markets as starting at $1.50 an hour. Managed storage is $0.024 per GB-month.

Its most useful feature for a small team: usage limits in RPU-hours that send an alert or block compute past a threshold. No other warehouse in this ranking makes a hard guardrail that simple. And with no queries running, there's no compute charge.

The traps: activity is billed for at least 60 seconds at a time, storage is billed even when nothing runs, and for a steady all-day workload a provisioned cluster (an ra3.4xlarge is $3.26 an hour in US East) often beats Serverless. Older cost estimates floating around blogs assume the old 8 RPU minimum; redo yours with 4.

New accounts get $300 in credit to use within 90 days on a first Serverless warehouse, enough to load your data and check your queries before paying.

MotherDuck is the cloud version of DuckDB, the small analytical database plenty of analysts already run on their laptops. One query can join local files with tables in the cloud.

The Lite plan is free: 3 users, 10 GB of storage and 10 compute hours a month, no card. Past that, Business is $250 a month per organization plus usage: $0.60 per CU-hour on Pulse (billed per query), $2.40 an hour for a Standard instance, up to $24 for the largest. Storage is $0.04 per GB-month.

One thing to get right on day one: the region is set when you create the organization and can't be changed later. If your data must stay in a given region, create the account there.

Its limits: a younger ecosystem than the big four, fewer ready-made connectors, and an engine that isn't built for hundreds of concurrent users. And the flat $250 for Business is a steep jump the moment you outgrow the free plan.

Fabric bundles Microsoft's data tools (warehouse, the OneLake data lake, pipelines, Power BI) into one platform billed by capacity. You buy an F size (F2, F4, F8…) and every workload draws from it.

Microsoft's pricing page doesn't show a readable monthly figure for F2, so we calculated it ourselves from the official hourly price of a capacity unit: about $0.18 per CU-hour in East US. An F2 has 2 CUs: 2 × $0.18 × 730 hours comes to about $262.80 a month if it runs the whole month. A one- or three-year reservation saves about 41%. OneLake storage runs $0.026 per GB-month in East US.

Trap one: on pay-as-you-go, you pay for the capacity until you pause it, even if nobody uses it. Trap two: on small capacities, a spike gets paid back later. Fabric smooths some background operations over 24 hours, and F2 users on the official community forum describe being throttled for close to a day after going over, with very slow queries.

Its real argument: if your reports are in Power BI and your users in Microsoft 365, everything connects without a third-party tool.