Skip to content
Lakehouse Compare

Guide, read 10 Nov 2026

Databricks vs Snowflake: the published facts, by situation

All guidesOpen the Compute Bill

Running existing Spark batch code

Databricks runs Apache Spark in its own runtime. Its release notes list Databricks Runtime 18 LTS with Apache Spark 4.1.0 (released June 10, 2026), Runtime 17.3 LTS with Spark 4.0.0, and Runtime 16.4 LTS and 15.4 LTS with Spark 3.5.x. Runtime 19 ships Spark 4.2.0 (July 23, 2026). Photon, its native C++ engine, keeps the Catalyst planner and falls back to the Spark runtime for unsupported operations.

Snowflake does not run a Spark cluster. Snowpark Connect for Apache Spark sends PySpark DataFrame code over the Spark Connect protocol to a Snowflake warehouse, and batch jobs go in through the Snowpark Submit CLI. Snowflake documents support for Spark 3.5 only; code written for 3.4 or earlier, or for 4.0 and later, is listed as unsupported. The compatibility page lists DayTimeIntervalType, YearMonthIntervalType and user-defined types as unsupported.

On Databricks serverless compute, only Spark Connect APIs are supported. RDD APIs, R, Maven coordinates and Databricks Container Services are listed as unsupported, ANSI mode is on by default and the default time zone is UTC. Either vendor can change results of an existing job; test a copy first.

Billing units

Databricks bills in DBUs, a normalized unit of processing power, per second, with pay-as-you-go or committed-use discounts. Photon instance types use DBUs at a different rate than the same instance without Photon. The pricing pages render their rates by script; the data file behind the pricing calculator lists Jobs Compute on AWS at $0.15 per DBU on the Premium plan and $0.20 on Enterprise, and 4.08 DBU per node-hour for r6i.4xlarge (read 2026-11-10).

Snowflake bills credits per second with a 60-second minimum each time a warehouse starts, and each size step roughly doubles the credits per hour (an XL standard warehouse is 16). Snowflake's Service Consumption Table, effective 2026-11-09, lists $2.00, $3.00 and $4.00 per credit for Standard, Enterprise and Business Critical on AWS US East (Northern Virginia). A per-DBU rate for Databricks: none found on 2026-11-10, so the two vendors' dollar rates are not set against each other here; see lakehouse pricing models.

Table formats and open storage

Databricks documents Delta Lake as its native format. UniForm lets Delta tables generate Iceberg metadata from Databricks Runtime 14.3 LTS so Iceberg clients can read them without rewriting data files.

Snowflake supports Iceberg tables in Parquet with data in customer-managed S3, Google Cloud Storage or Azure storage through external volumes, with an external catalog integration such as AWS Glue. Delta files are read through Delta Direct. Hudi was not listed on the Snowflake page read. Compare the formats themselves on the Iceberg vs Delta Lake page.

Table maintenance

Databricks predictive optimization runs OPTIMIZE, VACUUM and ANALYZE automatically on Unity Catalog managed tables, Delta and Iceberg, and is on by default. It uses serverless compute and is billed through a serverless jobs SKU. It does not apply to tables outside Unity Catalog management.

For Snowflake-managed Iceberg tables, Snowflake documents data compaction as on by default and billable, manifest compaction and snapshot expiry as automatic with no cost, and Automatic Clustering as off by default and billed separately. For Iceberg tables managed by an external catalog, Snowflake states it performs no maintenance and you must run compaction and snapshot expiry in your own engine.

Cloud and region coverage

Databricks runs on AWS, Azure and Google Cloud. The AWS region page lists regions including us-east-1, us-east-2, us-west-1, eu-west-1, eu-central-1, ap-southeast-2 and us-gov-west-1, and notes some features exist only in a subset of regions.

Snowflake also runs on all three clouds. Its AWS regions include us-east-1, us-west-2, eu-west-1 and ca-central-1, and each account is hosted in a single region.

Published performance claims

Databricks announced an audited 100 TB TPC-DS result of 32,941,245 QphDS for Databricks SQL on November 2, 2021, which it says is 2.2 times the previous record held by Alibaba, with total system cost 10% lower on list pricing. It is a SQL warehouse result, not Spark batch ETL, and Databricks ran it. The same post cites research it attributes to the Barcelona Supercomputing Center; that study was not fetched.

For Spark batch jobs on Snowpark Connect, no published benchmark with a stated method was found on 2026-11-10. For Databricks, none was found for Spark batch ETL with a method either, apart from the vendor claim that Photon gives up to 5 times better price/performance than other cloud data warehouses, which the documentation states without a method.

Sources

  1. Databricks Runtime release notes, read 10 Nov 2026
  2. Databricks Photon, read 10 Nov 2026
  3. Databricks serverless compute limitations, read 10 Nov 2026
  4. Databricks UniForm, read 10 Nov 2026
  5. Databricks predictive optimization, read 10 Nov 2026
  6. Databricks blog, TPC-DS record, 2021-11-02, read 10 Nov 2026
  7. Databricks supported regions, read 10 Nov 2026
  8. Databricks pricing data file (AWS), loaded by its pricing calculator, read 10 Nov 2026
  9. Snowpark Connect for Apache Spark, read 10 Nov 2026
  10. Snowpark Connect limitations, read 10 Nov 2026
  11. Snowpark Connect compatibility, read 10 Nov 2026
  12. Snowflake compute cost, read 10 Nov 2026
  13. Snowflake Iceberg tables, read 10 Nov 2026
  14. Snowflake Iceberg table management, read 10 Nov 2026
  15. Snowflake regions, read 10 Nov 2026
  16. Snowflake Service Consumption Table, read 10 Nov 2026

Last reviewed 10 Nov 2026.