Hello Shivam Kumar
Welcome to the Microsoft Q&A and thank you for posting your questions here.
Sequel to your questions, I understand that you're encountering error after the Azure SQL database data source scan in Purview as listed above and you want to resolve these issues.
After analyzing the errors you're encountering, it shows that the Azure SQL database data source scan in Purview suggest that there are issues with accessing or querying certain objects or columns within your database. The breakdown of the errors are as follows in three type:
- Errors indicate that the specified object (table, view, etc.) cannot be found in the database. It seems that Purview is trying to access objects like 'qr-edp-data.thitiwut_wanvisut_edp_silver_dfm.commercial_tenant_detail_filter' and similar ones, but they don't exist in the database or are inaccessible, so, this will be an Invalid object name to Purview.
- Sencondly, it suggests that there's a mismatch between the number of columns specified and the number of columns defined in the view or function 'edp_gold_gpm.property_overview'. This could be due to a discrepancy in the definition of the view or function.
- Also, Invalid column errors indicate that there are columns referenced in queries that don't exist in the corresponding tables. For example, columns like 'p_itype' and 'p_hmy' are being referenced but are not found in the tables being queried.
To resolve these errors, you'll need to investigate and address the underlying issues in your database:
- Ensure that the objects are accessible to the user or service account used by Purview for scanning.
- Review the definition of the view or function mentioned in the error with more column names specified than defined. This is to be sure that the number of columns specified matches the number defined.
- Verify the existence and correctness of the column names referenced in the queries. If columns are missing or incorrectly referenced, correct the queries accordingly.
After you addressed these issues in your database, you can rerun the scan in Purview to see if the errors are resolved. The credentials you used for Purview is very important in your case.
You can also, read more in the additional resources by the right pane of this page.
I hope this is helpful! Do not hesitate to let me know if you have any other questions.
Please remember to "Accept Answer" if answer helped, so that others in the community facing similar issues can easily find the solution.
Best Regards,
Sina Salam