← Back to home
Comparison · Analytics

dbt Core vs soilDBdata

A side-by-side editorial comparison of dbt Core and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.

dbt Core vs soilDBdata: at a glance

Featuredbt CoresoilDBdata
SectorAnalyticsAnalytics
Velocity score6.30.0
Sparks · 30d00
Top themesanalytics-engineering, dbt-fusion, adapters, clickhousesoil data, test fixtures, nasis, data package
Last editorial update10h ago2d ago
WebsiteVisit →Visit →

What is dbt Core?

dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs

Fusion 2.0 is in its second beta, and the content has shifted from engine capability to adapter coverage. beta.2 is almost entirely ClickHouse — Dictionary materialization, index definitions, additional settings, a relation-scoped catalog macro that fixes --write-catalog, and a seed nullability fix — plus Entra bearer-token authentication for the Fabric adapter. Behind it sits the August 14 backport wave, which cut releases for 1.1 through 1.8 in a single day to deliver one deprecated-version warning.

Read the full dbt Core trajectory →

What is soilDBdata?

soilDBdata exists so soilDB's tests can run without a NASIS connection.

soilDBdata is a data-only package supplying NASIS and gSSURGO sample datasets as .sqlite assets, installed separately by soilDB's GitHub Actions so unit tests that would otherwise need database access can run. It began as a proof of concept carrying MT663 pedon and component tables used in soil survey coursework, and its most recent release adds a Marshall Islands FY26 gSSURGO dataset. Releases are infrequent and driven by what the parent package needs to test.

Read the full soilDBdata trajectory →

dbt Core vs soilDBdata: editorial side-by-side

D
dbt Core
ANALYTICS
6.3

dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs

◆ Current state

Fusion 2.0 is in its second beta, and the content has shifted from engine capability to adapter coverage. beta.2 is almost entirely ClickHouse — Dictionary materialization, index definitions, additional settings, a relation-scoped catalog macro that fixes --write-catalog, and a seed nullability fix — plus Entra bearer-token authentication for the Fabric adapter. Behind it sits the August 14 backport wave, which cut releases for 1.1 through 1.8 in a single day to deliver one deprecated-version warning.

◆ Where it's heading

The two ends of this project are pulling apart cleanly. Old branches are being prepared for retirement — a deprecation warning fanned across eight of them, Python 3.8 testing dropped from 1.4 through 1.6 — while Fusion accumulates the adapter breadth it needs to be a credible replacement. beta.1 proved the engine could bind without a catalog; beta.2 is the unglamorous follow-through of making a specific warehouse work properly.

◆ Prediction

Expect further beta releases filling in per-adapter gaps rather than new engine capability, and formal end-of-life notices for the branches that just took the deprecation warning.

S
soilDBdata
ANALYTICS
0.0

soilDBdata exists so soilDB's tests can run without a NASIS connection.

◆ Current state

soilDBdata is a data-only package supplying NASIS and gSSURGO sample datasets as .sqlite assets, installed separately by soilDB's GitHub Actions so unit tests that would otherwise need database access can run. It began as a proof of concept carrying MT663 pedon and component tables used in soil survey coursework, and its most recent release adds a Marshall Islands FY26 gSSURGO dataset. Releases are infrequent and driven by what the parent package needs to test.

◆ Where it's heading

Development follows soilDB rather than leading it: assets get bumped when a soilDB version changes, and purpose lists are updated when soilDB adds a table. The one release that changed what testing is possible was v0.1.1, which added selected-set _View_1 tables alongside whole tables so both SS=TRUE and SS=FALSE code paths could be exercised. Four-year gaps between releases are normal here and do not indicate abandonment — a fixture package only needs to move when the fixtures go stale.

◆ Prediction

The recent addition is a new geography rather than a new table structure, so further releases most likely continue broadening dataset coverage as soilDB gains regions to test against.

Alternatives to dbt Core and soilDBdata

Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either dbt Core or soilDBdata.

See all dbt Core alternatives → · See all soilDBdata alternatives →

Recent activity from dbt Core and soilDBdata

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agodbt CoreFusion beta.2 fills in ClickHouse materializations and catalogs
  2. 5d agodbt Coredbt 1.2.7 backports the deprecated-version warning and old fixes
  3. 5d agodbt Coredbt 1.1.6 backports the deprecated-version warning and old fixes
  4. 5d agodbt Coredbt 1.3.8 backports the deprecated-version warning
  5. 5d agodbt Coredbt 1.4.10 drops Python 3.8 and warns on deprecated versions
  6. 6d agodbt Coredbt 1.5.12 drops Python 3.8 and warns on deprecated versions
  7. 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
  8. 1y agosoilDBdataMT663 fixtures refreshed for soilDB 2.8.3
  9. 1y agosoilDBdataNASIS purpose lists updated for siteothvegclass
  10. 4y agosoilDBdataSelected-set _View_1 tables enable SS=TRUE/FALSE testing
  11. 4y agosoilDBdataProof of concept: MT663 pedon and component .sqlite fixtures

Frequently asked questions

What is the difference between dbt Core and soilDBdata?

They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is dbt Core better than soilDBdata?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbt Core is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to dbt Core?

Top dbt Core alternatives in Analytics are ranked by recent ship velocity. Browse the "dbt Core alternatives" section above for the current picks, or visit /alternatives/dbt-core for the full list with editorial commentary on each.

What are the best alternatives to soilDBdata?

Top soilDBdata alternatives in Analytics are ranked by recent ship velocity. Browse the "soilDBdata alternatives" section above for the current picks, or visit /alternatives/soildbdata for the full list with editorial commentary on each.