What tables should an ADF and Power BI dependency database start with?

Start with artifacts, dependencies, snapshots, owners, and release gates. Artifacts describe pipelines, activities, datasets, linked services, triggers, SQL objects, semantic models, reports, dashboards, schedules, and workspaces. Dependencies describe source-target relationships, confidence, extraction method, and review state.

Do we need a graph database for reporting dependency analysis?

Not at first. A relational schema or CSV export can prove the artifact and edge model. A graph database becomes useful when teams need deeper path queries, multi-hop traversal, or interactive lineage views at larger scale.

Can this be built without production report data?

Yes. The first version can use metadata-only exports, redacted names, hashes, synthetic fixture reports, and read-only snapshots. Production report contents, credentials, customer records, and private metrics should stay out of discovery until access and handling rules are explicit.

Loading Closeaim experience

Closeaim Software Solutions

Data automation · 2026-06-17

ADF and Power BI dependency database architecture

A useful reporting dependency database turns ADF JSON, SQL dependency metadata, Power BI lineage, owners, schedules, and snapshots into one reviewed graph for impact analysis.

Book discovery View solution map