I was able to set up scans for on-prem SQL databases using a registered source without an instance name. We have a server with 4 DBMS Instances on a single server. When I declare the non-default instance in the registered source per the example. The scans look like they set-up correctly (connection test suuccessful) but no assets are returned in the scan.

Hello @Everett, Andy , The product team has been fixed the issue in the latest version of the SHIR. Could you please update SHIR to the latest version and try again? Hope this helps. Do let us know if you any further queries. ------------ Please accept an answer if correct. 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 .

Issue scanning on-prem SQL DBMS Instances (non-default)

Accepted answer

PRADEEPCHEEKATLA-MSFT 78,986 Reputation points Microsoft Employee

2021-01-08T07:06:33.953+00:00
Hello @Everett, Andy ,

The product team has been fixed the issue in the latest version of the SHIR.

Could you please update SHIR to the latest version and try again?

Hope this helps. Do let us know if you any further queries.

------------

Please accept an answer if correct. 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.
Please sign in to rate this answer.
Everett, Andy 166 Reputation points

2021-01-08T17:57:09.343+00:00

Is there documentation for updating SHIR in place? All I've seen is how to create a SHIR.

PRADEEPCHEEKATLA-MSFT 78,986 Reputation points Microsoft Employee

2021-01-11T11:22:42.847+00:00

Hello @Everett, Andy ,

You may check out this article: Automating self-hosted integration runtime installation using local PowerShell scripts.

Hope this helps.

PRADEEPCHEEKATLA-MSFT 78,986 Reputation points Microsoft Employee

2021-01-18T08:55:10.243+00:00

Hello @Everett, Andy ,

Just checking in to see if the above answer helped. If this answers your query, do click “Accept Answer” and Up-Vote for the same. And, if you have any further query do let us know.

PRADEEPCHEEKATLA-MSFT 78,986 Reputation points Microsoft Employee

2021-01-19T12:28:45.293+00:00

Hello @Everett, Andy ,

Following up to see if the above suggestion was helpful. And, if you have any further query do let us know.

Take care & stay safe!

Everett, Andy 166 Reputation points

2021-01-19T19:33:16.993+00:00

Yes, It did help. We updated the SHIR and are now able to scan the non-default DBMS instances

PRADEEPCHEEKATLA-MSFT 78,986 Reputation points Microsoft Employee

2021-01-20T03:50:02.793+00:00

Hello @Everett, Andy ,

Glad to know your issues have resolved.

If the above answers were helpful, click “Accept Answer” or “Up-Vote”, which might be beneficial to other community members reading this thread.

PRADEEPCHEEKATLA-MSFT 78,986 Reputation points Microsoft Employee

2021-01-20T12:30:40.57+00:00

Hello @Everett, Andy ,

Please do remember to click on "Accept Answer" and Upvote on the post that helps you, this can be beneficial to other community members.

------------

Please accept an answer if correct. 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.
Sign in to comment

Share via

Issue scanning on-prem SQL DBMS Instances (non-default)

0 additional answers