lineage and more

Hi db042190, what you’re describing is very doable, but usually with a catalog/lineage platform, not just Fabric alone.

1) The SSIS lineage product you may be thinking of

The product that many large enterprises used for deep SSIS lineage is Manta, now IBM Automatic Data Lineage.

Other common enterprise options:

• Collibra Data Lineage
• Dataedo
• Microsoft Purview
• Atlan
• DataHub

For SSIS specifically, these tools can parse packages, transformations, and source/target mappings.

2) Can Fabric lineage visuals be turned into database-backed data?

Not directly from the visual itself.

Fabric’s lineage view is primarily a UI presentation of metadata.
If you want database-backed lineage, the normal pattern is to extract metadata through APIs/scanners and store it in your own catalog or governance store.

Useful Microsoft docs:

• Fabric lineage overview:
  https://learn.microsoft.com/en-us/fabric/governance/lineage
• Fabric + Purview lineage:
  https://learn.microsoft.com/en-us/purview/data-map-lineage-fabric

So the answer is:

• Yes, lineage can be captured
• No, the visual itself is not usually the database source of truth
• You typically build or buy a catalog that stores the lineage edges and attributes

3) Can Power BI lineage be captured and stored somewhere?

Yes.

Power BI metadata can be harvested using the Power BI Admin APIs, and Microsoft Purview can also collect Power BI lineage.

Docs:

• Power BI Admin workspace scan API:
  https://learn.microsoft.com/en-us/rest/api/power-bi/admin/workspace-info-post-workspace-info
• Power BI lineage in Purview:
  https://learn.microsoft.com/en-us/purview/data-map-lineage-power-bi

So for Power BI service content:

• reports
• datasets/semantic models
• dataflows
• dashboards

…you can absolutely capture lineage and store it in a catalog.

4) What about SSRS / Power BI Report Server?

Yes, but it is usually less automated and less rich than cloud Power BI or Fabric.

Microsoft has guidance around separating report and model logic:

• https://learn.microsoft.com/en-us/power-bi/guidance/report-separate-from-model

For SSRS / PBIRS, many organizations use third-party tools to scan the catalog and report definitions and then build lineage from there.

5) Can you map lineage all the way back to bronze and even earlier?

Yes, to a point.

A strong enterprise lineage stack can cover:

• source systems
• landing/bronze
• SSIS
• SQL views / stored procedures
• lakehouse / warehouse
• semantic models / Power BI
• SSRS / PBIRS

And in some cases it can go 1–2 layers upstream of bronze if the upstream systems expose enough metadata or SQL/script definitions.

The best-fit tools for that are usually:

• IBM Automatic Data Lineage / Manta
• Collibra
• Dataedo
• Purview for Microsoft-centric governance
• Atlan in modern data stacks