Unused Data Flows

Find tables that are actively written to by pipelines but never read — the upstream compute and orchestration cost is pure waste.

Overview

Unused Data Flows highlights tables that have active pipeline connections writing data into them but zero read activity over the analysis window. The upstream pipeline compute (dbt runs, Airflow tasks, Fivetran syncs) that feeds these tables is wasted spend.

---

How It Works

Detection Logic

Seemore checks two conditions for every table with at least one upstream pipeline:

1. Active pipeline connection — the table appears as a destination in a tracked pipeline that has run within the analysis window.

2. Zero reads — no SELECT queries have been executed against the table during the same period.

Tables meeting both criteria are flagged as unused data flows.

---

Upstream Lineage Analysis

For each flagged table, Seemore traces the full upstream lineage to identify:

• All pipeline steps that contribute to populating the table.

• Associated compute cost of those pipeline runs.

• Related tables and views that exist solely to feed the unused destination.

This helps you understand the total blast radius of removing the data flow.

---

Cost Estimation

Each insight includes:

• Estimated annual compute savings from stopping the pipeline.

• Row count reduction and storage freed by dropping the destination table.

---

Remediation

1. Verify with the table owner that no downstream consumers exist outside of Seemore's visibility.

2. Disable or remove the pipeline step that writes to the table.

3. Optionally drop the destination table to reclaim storage.

4. Mark the insight as Done in Seemore.

---

Configuration

Parameter	Default	Description
Analysis window	21 days	How far back Seemore looks for read activity and pipeline runs.

If you have configured Exclude Users from Usage, excluded users' reads are ignored. This means tables read only by service accounts or bots will still appear as unused data flows.