Azure SQL table scanning mislead in Azure Purview

Anto Reni Huxley Antokinsley 81 Reputation points

I created a table in my Azure SQL server(Server name: trail, DB Name: test, Schema Name: dbo ) as shown in the below screenshot

I registered the Azure SQL source in Azure purview and did a scan and the newly created table was scanned successfully but there was something unusual in the schema. There was another column created in the sql table (sample) column name: Sno. Not sure why this extra column populates. Is there any workaround for this particular?

Microsoft Purview
Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
467 questions
{count} votes

Accepted answer
  1. PRADEEPCHEEKATLA-MSFT 56,466 Reputation points Microsoft Employee

    Hello @Anto Reni Huxley Antokinsley ,

    This is expected behaviour due to recursive schema parsing with slashes (‘/’ or ‘\’) in the name.

    As of today, Azure Purview don’t support scanning SQL entities with slashes (‘/’ or ‘\’) in the name.

    Currently, we don’t have a workaround for this. Our guidance is to avoid scanning SQL entities with slashes in the name.

    Our product team is actively working on fixing this issue and I will update this thread once it available.

    Hope this will help. Please let us know if any further queries.


    • Please don't forget to click on 130616-image.png or upvote 130671-image.png button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is how
    • Want a reminder to come back and check responses? Here is how to subscribe to a notification
    • If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators

0 additional answers

Sort by: Oldest