Forum Discussion
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.
1 Reply
- Prathista Ilango
Microsoft
This is expected as fully qualified name is created based on the source of ingestion.
Currently Microsoft supports a list of normalization rules and automatically normalizes assets in case of duplication. However, your case might not fall under any of those categories or rules.
Refer to: Asset normalization in Microsoft Purview Data Map | Microsoft Learn
Please mark as solution, if you find the answer helpful. This will assist others in the community who encounter a similar issue, enabling them to quickly find the solution and benefit from the guidance provided.