The migration isn't blocked by the data.It's blocked by what depends on it

One column-level lineage graph across production systems, dbt, Airflow, Snowflake, Databricks, Redshift, BI tools such as Tableau, Power BI, and Looker. Understand all the implications of deprecating a legacy table.

datahub · decommission readinesslive
365 / 412
legacy tables with
zero readers in 90 days
47
still have live consumers
legacy_dw.dim_customer· 0 reads / 90dSafe to drop
legacy_dw.stg_payments· 0 reads / 90dSafe to drop
legacy_dw.dim_product· 0 reads / 90dSafe to drop
Open the blocked row to see the evidence a cutover decision needs, across four systems.
Trusted by modern data teams

A migration doesn't create the dependency problem. It exposes it

"What reads this table?" used to be answered by asking around, and that held up while nothing moved. Here is what four teams said the week a cutover date landed on them.

Recognize any of these? We'll walk the same situation through DataHub.

Book a demo

One graph. It doesn't stop at any tool's edge

Postgres
orders
Production source. A column definition changed here last Tuesday.
Airflow
ingest_orders
The DAG that moves it. Task-level lineage, captured automatically.
Databricks
bronze.orders
Landed raw in the lakehouse.
Databricks · dbt
silver_orders
Curated by a dbt model, materialized in Databricks.
Snowflake · dbt
mart_revenue
The mart the business reports from. Applies a different filter.
Tableau
Revenue Overview
What the CFO opens on Monday morning.

All seven hops, in one column-level graph. Change the Postgres column and DataHub names the Tableau dashboard that will be wrong on Monday, plus the dbt model, the Databricks table and the Snowflake mart in between.

One catalog across the estate, not one per tool

Unity Catalog, Snowflake Horizon and dbt's own docs are good at what they do. None of them is trying to be the catalog for the systems it doesn't own, which is why you ended up with three. Pick a tool to see what it covers, where its picture stops, and what a cross-system layer adds.

Consolidation here means one place to look, not one vendor to buy everything from. Can you still use Horizon if you use DataHub? Yes. Horizon manages the native Snowflake metadata surface, and the two are designed to work together. The same holds for Unity Catalog and for dbt. What you remove is the third and fourth general-purpose catalog nobody owns, and the spreadsheet that reconciles them.

Ask where the boundary sits for a stack like yours. We'll show you in the product.

Book a demo

Connecting Snowflake is three SQL statements and a scheduled run

snowflake · datahub setup
-- 1. a role for DataHub to read metadata with
create role if not exists datahub_role;
grant operate, usage on warehouse "COMPUTE_WH"
  to role datahub_role;

-- 2. the service user it connects as
create user datahub_user
  display_name = 'DataHub'
  type          = LEGACY_SERVICE
  default_role  = datahub_role;

-- 3. read-only metadata grants, per database
grant usage on database "<database>" to role datahub_role;
grant usage on all schemas in database "<database>"
  to role datahub_role;
grant select on all tables in database "<database>"
  to role datahub_role;
grant references on all views in database "<database>"
  to role datahub_role;
grant imported privileges on database snowflake
  to role datahub_role;
Abridged from the DataHub Snowflake quick ingestion guide. Run by someone holding ACCOUNTADMIN or MANAGE GRANTS.
01
Grant read access to metadata

Three statements: a role, a service user, and read-only grants per database. Nothing writes back to the warehouse.

02
Point the connector at it

Configure the recurring ingestion pipeline in the UI or in YAML, then schedule it. It pulls databases, schemas, tables, external tables, views and materialized views.

03
Lineage and usage arrive with it

Table and column lineage, usage statistics from recent query activity, and table profile statistics come from the same connection. Where a platform has no native tracking, the SQL parser reads the query log instead.

04
Add the next system, then the next

dbt, Airflow, Databricks, Redshift, Looker, Tableau and Power BI each connect the same way. The graph joins them automatically: one estate, added a platform at a time.

120+ connectors, so the graph covers the whole migration

Every system on both sides of the cutover, plus the tools reading from them.

Counts from the DataHub connector directory, which also covers data lakes, messaging, data quality, AI/ML and identity.

Want to see the whole thing working end to end?

Book a demo

DPG Media cut Snowflake costs 25% a month by finding what nobody was using

Eight catalogs evaluated. One estate, finally, with an owner

DPG Media grew by acquisition, and every acquisition brought new systems and overlapping data into the group. The team had been operating much like a data mesh already, but without any form of governance on top of it. Once DataHub Cloud made usage and duplication visible across Snowflake, Redshift, Looker, Tableau, Qlik, Kafka, Spark, Airflow and dbt, they could identify and eliminate unused and duplicate data, and take the warehouse bill down with it.

"With DataHub, we were able to reduce our Snowflake costs by 25% each month."
ML
Mathias Lavaert
Principal Data Engineer, DPG Media

Commercially validated by Snowflake

Premier Data Cloud Product Partner
Snowflake Ready Technology
Snowflake Horizon Partner

The stack DataHub had to span

A real consolidation estate, not a single-warehouse demo.

SnowflakeRedshiftdbtAirflowSparkKafkaLookerTableauQlikAWS

Sources: DPG Media customer story and the DataHub Snowflake partnership page.

Book your custom demo with DataHub

Share a few details about your goals, and we'll be in touch to schedule a personalized walkthrough tailored to your data environment, use cases, and roadmap.

We'll cover:

How DataHub helps teams discover, understand, maintain, and govern their data
Best practices for driving adoption across your org
How to get started fast, with cloud-native or on-prem deployment

Let's get you the answers and insights you need.

Self-hosted or cloud/SOC 2 Type II/Snowflake Premier Partner

Share a few details

A DataHub specialist will be in touch to schedule your walkthrough. Takes 30 minutes, no prep required.

No prepNo data required

Prefer to look around first?
Take the self-guided product tour

No data required. Demos run in a DataHub environment on a realistic estate. Nothing connects to your systems, and we don't work from data you provide.