Purview: SQL Server scan results in 0 assets

Eugen Buzyuma 6

We scan SQL Server (on-prem) via self-hosted integration runtime (SHIM), it is on-prem as well.

The connection between SQL server and SHIM works: I see tables during scan setup.
The scan runs smoothly as well: I see "Assets Ingested xx processing".
Data Ingestion takes about 5 minutes and Scan takes about 7 minutes.
After that, there are zeros reported for Assets classified, Assets discovered, Assets ingested and Relationships ingested.
It is the first and full scan.

There is already a similar question, but in our case seems that connectivity and access are not the issues.
Also, I would say that it is unexpected behaviour when SHIR fails to access a storage or a data source but the scan is still reported as successful.

I reviewed the event logs of SHIM, and there is nothing outstanding during scan execution.

What do I miss?
Is there a case when a Table won't be added as an asset?

BhargavaGunnam-MSFT 26,136 Reputation points Microsoft Employee

2022-11-28T19:26:54.807+00:00

Hello @Eugen Buzyuma ,

Welcome to the MS Q&A platform.

Were you able to discover the assets before with the same setup? Can you please confirm, if your purview account is behind private endpoints?

If yes, It could be private endpoints aren't set up correctly for the data source. Please check if you allowed trusted Microsoft services enabled and follow this doc

https://learn.microsoft.com/en-us/azure/purview/catalog-private-link#enable-a-private-endpoint-on-existing-azure-purview-accounts
Eugen Buzyuma 6 Reputation points

2022-11-30T14:31:43.533+00:00

Nope, haven't gotten this setup working yet. Just started to configure Data Sources.

Inside Azure network, it works, assets were found for Azure Data Lake Storage.

And indeed, we use private endpoints.
As per the documents, you've shared, am I reading it right that Windows Authentication for SQL Server via Self-Hosting integration runtime will not work?
Eugen Buzyuma 6 Reputation points

2022-11-30T15:06:37.05+00:00
Also, a storage account is reachable from the integration runtime.

The command like:

Test-NetConnection -ComputerName `<purview_related_storage>`.blob.core.windows.net -Port 443

Reported succeeded.

TcpTestSucceeded: True
BhargavaGunnam-MSFT 26,136 Reputation points Microsoft Employee

2022-11-30T22:04:14.55+00:00

Hello @Eugen Buzyuma ,
I have discussed the issue with my internal team. As per them, you will need to map the ingestion private endpoint for your purview account, and You will be able to discover the assets after that.

Please see the below document for your reference:
https://learn.microsoft.com/en-us/azure/purview/catalog-private-link

Please let me know if you have any further questions.
BhargavaGunnam-MSFT 26,136 Reputation points Microsoft Employee

2022-12-03T01:28:20.283+00:00

Hello @Eugen Buzyuma ,
I am checking to see if you got a chance to look into my above response. Please let me know if you have further questions.
Eugen Buzyuma 6 Reputation points

2022-12-06T13:49:35.097+00:00

Hi, we are going through the troubleshooting guide and double-checking that everything is setup according to the documentation.
Haven't resolved the problem yet.

What exactly should I do "to map the ingestion private endpoint for your purview account"? I do not quite understand.
According to the initial investigation, from IR connection to purview, private ingestion endpoints are possible.

Just in case, tried SQL Authentication instead of Windows authentication and same result.
This is the last run id 6af6cd13-5001-475b-bc8c-c7792cf5f77f, if it will say more information to you.
BhargavaGunnam-MSFT 26,136 Reputation points Microsoft Employee

2022-12-07T23:21:53.033+00:00

Hello @Eugen Buzyuma ,
Here is my understanding from the documentation page. The private endpoint is only to access purview if public access is disabled, and the Ingestion private endpoint is to connect with SHIR VNet so that purview can scan private resources.
Please let me know if you have any further questions.