Forum Discussion

Deleted's avatar
Deleted
May 12, 2025

Same Assets two different Qualified Names.

I scanned assets in Microsoft Purview using two methods:
1. Importing assets directly from an on-prem SQL Server
2. Importing lineage from Azure Data Factory
However, Purview is tagging the fully qualified names differently for each method, which is causing it to treat the same dataset as two separate assets. The Onprem one has a prefix of "MSSQLSERVER"Infront of the DB name.
I've attached screenshots for more context.

Is this the default behavior? If yes, how do I override it?
Or is there any other solution for this one.

 

No Replies

Resources