locked
SQL DB Server are not discoverd in new MP RRS feed

  • Question

  • Hi,

    we have imported the new version of SQL MP 7.0.20.0 and our sql server wont get discovered in the "new" view.

    After importing the new mp we have two folders SQL and SQL (old).

    In the old folder our sql server 2016 are listed correct and monitoring works as expected.

    In the "new" folder we only see our scom reporting server with SQL 2016 and no other SQL 2016 or SQL 2017 at all.

    We filled all sql discovery profiles with the correct accounts and deployed the accounts to our sql server.

    There is no error or warning in the alerting pane and the new seed classes are empty, except our scom reporting server.

    We checked our overrides and there is also no exclude list or disabled discovery.

    Any idea ?

    regards,

    steffen

    Friday, January 24, 2020 2:21 PM

All replies

  • Hi,

    If you're not using SQL Servers older than 2012, I would suggest you completely switch to the new SQL Server version agnostic management pack (the one you just imported).

    You can refer to Kevin's blog post here:

    How to transition to the SQL Version Agnostic MP
    https://kevinholman.com/2019/06/12/how-to-transition-to-the-sql-version-agnostic-mp

    From Kevin's blog post:

    "If you were previously using the older MP’s for 2012-2016, there is a process you will need to plan for, in transitioning.  This article is a step by step plan on how to make the transition from the Legacy MP’s to the new Agnostic MP’s with the least duplication of alerting, and load on SCOM."

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, January 24, 2020 2:25 PM
  • Thanks for the feedback but that is not my problem.

    we havent excluded any SQL Version in the new mp and SQL 2017 is not getting discovered at all.

    also we only have the new SQL mps with version 7.0.20.0 and some explicit SQL 2016 mp

    with Version 7.0.15.0 (that is the "old" one) which is working but cant monitor SQL 2017.

    the main problem is why does the new mp cant find all our SQL 2016 instances and the SQL 2017 instances ?

    Friday, January 24, 2020 3:20 PM
  • Are they clustered instances?

    Do you see any error in the operations manager event log on the SQL servers?

    Friday, January 24, 2020 3:25 PM
  • The discoveries run every 14400 seconds (4 hours) by default, so it could be that it has not run yet.
    You can manually run a discovery or create an override for the DB Engine Seed for a faster discovery frequency.
    Manually Trigger Object Discoveries in SCOM

    If you're sure the discovery has run, check the Operations Manager event log for any errors.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, January 24, 2020 3:27 PM
  • Hi,

    We can follow the steps in the following link to do troubleshooting:

    1.Check the target of the discovery rule
    2.Check the health state of Windows agent.
    3.Check if the discovery is overridden
    4.Check the Run As account that's running the discovery
    5.Examine the Operations Manager event log on the agent for errors

    https://support.microsoft.com/en-hk/help/4089249/troubleshoot-sql-database-discovery-in-operations-manager


    Hope it can help.

    Best regards.
    Crystal

      

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, January 27, 2020 1:52 AM
  • Hi,

    How's everything going? Could you check the information? Is there any update on our issue? If yes, feel free to let us know.

    Best regards.

    Crystal


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, January 30, 2020 6:22 AM