question

Jonathan-4509 avatar image
0 Votes"
Jonathan-4509 asked 52866840 answered

SCOM 2019 and SQL 2019 Discovery Issues

I am new to Operations Manager and have started playing around with it for work. I have been through a couple of install/configuration iterations my first was with SCOM 2016 on a 2016 SQL server, and I was able to get some pretty detailed info out of my 2016 SQL Server but nothing higher. We run several environments with SQL 2019 so I tried to import the SQL Server Agnostic MP and still didn't detect the servers I was looking for just anything 2016 and under. So after a hardware failure I decided to give SCOM 2019 try to see if maybe I just needed the newer version to see my 2019 SQL servers and after a mishap with installing SQL 2019 as my SCOM DB server I fell back to SQL 2017. I installed the SQL Server Agnostic MP and I had info show up for a couple of 2012 SQL Servers and my SCOM 2017 SQL Server but still nothing for my 2019 SQL Servers.

I went to the Override Properties of MSSQL on Windows: Discover SQL Server Database Engines (Local) and there are no exclusions listed.

I noticed in Discovered Inventory under State Actions>Change Target Type I do not have and Lightweight SQL Server 2019 entries just 2012-2017.
51810-image.png

So I need help, can someone tell me what I am doing wrong?

Thanks,

Jonathan


msc-operations-manager
image.png (32.8 KiB)
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@Jonathan-4509, From your description, I know the SQl 2019 is not discovered fter importing SQL agnostic MP. If there's any misunderstanding, please let us know.

Could you let us know if the MP we imported is with version 7.0.24.0
https://www.microsoft.com/en-us/download/details.aspx?id=56203

Did we see any error under Operations Manager event log?

0 Votes 0 ·

Crystal-MFST, First thank you for getting back to me !

Ok so here are all of my SQL Related MP currently.
52316-image.png




I looked back through the event viewer at the time of import, I had no errors.

0 Votes 0 ·
image.png (66.5 KiB)
Crystal-MSFT avatar image
0 Votes"
Crystal-MSFT answered Jonathan-4509 commented

@Jonathan-4509, From the picture you provided, I find the version 7.0.24.0 MP is included. Also, please check if we have configure the service SID, if not, please import the MP in the following link and finish all the configuration to see if it can fix our issue:
https://kevinholman.com/2016/08/25/sql-mp-run-as-accounts-no-longer-required/
Note: Non-microosft link, just for the reference.

Hope it can help.


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@Jonathan-4509, Hope things are going well. If there's any update, feel free to let us know.

0 Votes 0 ·

Sorry its taking me so long to respond but getting the HealthService Account added to SQL Server as part of this solution has turned a bit bureaucratic if you get my drift. We have several compliance rules we have to adhere to and I am waiting on a debate to finish before I can proceed.

0 Votes 0 ·
Jonathan-4509 avatar image
0 Votes"
Jonathan-4509 answered CyrAz commented

So we moved forward with this today and currently I am at a waiting point. We imported the MP, my database servers showed up under the SQL Seed Class, I took one and did the Health Service account SID change to it and it shows up as Healthy now, however it does not appear in the SQL DB Engine on Windows view. I did go to the host and double checked the status of the service and it is correct and I had a DBA add the NT Service\HealthService Account to the Login for SQL. His response was "Done, I didn't add any grants and the only default is "Connect". So I am not sure whats got me hung up right now. The server we did this on is a Windows 2012 r2 machine with SQL 2012 installed.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@Jonathan-4509, Thanks for the reponse. In my environment, I have tried to so the test. After importing the MPs, enable HealthService SID and create Health Service login. I also tried to enable the following discovery under SCOM authoring->Management Pack Objects->Object Discoveries
54822-image.png
54762-image.png

I found the Database and Database Engine of SQL 2019 can be discovered under "Database Engines" and "Databases"
54722-image.png


0 Votes 0 ·
image.png (11.8 KiB)
image.png (7.7 KiB)
image.png (90.6 KiB)

These two discoveries are absolutely not required to discover and monitor the databases, and actually the health service SID si not required either, it's just a best practice.
However what is required is some way of providing permissions to the SCOM database on the SQL instances and databases, but this is fairly well documented in the MP doc.

0 Votes 0 ·
52866840 avatar image
0 Votes"
52866840 answered

I had the exact same problem. The new version agnostic MP was discovering seeds but not any db instances or dbs.

The new MP has a filter to ignore previous SQL versions '2012,2014,2016' on the...

 'MSSQL on Windows: Discover SQL Server Database Engines (Local)' object.


I mistakenly added 2019 to this filter list (thinking it was an include list), then removed it again shortly afterwards.

This seems to have fixed my problem?? dbs and db engines are now coming in.

To clarify the filter is exactly as it was '2012,2014,2016'.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.