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 or upvote 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