locked
Whats the dependency of Microsoft.SQLServer.Library.mp on SQL2016 MP RRS feed

  • Question

  • Hi all,

    As we are aware that 2016 MP doesn't have Microsoft.SQLServer.Library.mp which was part of earlier versions of SCOM. Now we want to add 2016 MP to SCOM environment, any idea how would the rule tied up to library.mp would be used to monitor the 2016 servers as this MP <g class="gr_ gr_609 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="609" id="609">doesnt</g> exist anymore.

    Thanks


    Friday, November 3, 2017 7:06 AM

All replies

  • Hey,

    "which was part of earlier versions of SCOM."  You are partially correct: This particular library MP is part of the current version of the SQL MP for SQL Server 2008, 2008 R2 and SQL Server 2012. The MP is to be found here:

    Microsoft System Center Management Pack for SQL Server

    It is ment to be used on SCOM 2016 also. It is not outdated, it is just developed for SQL versions, other than SQL Server 2016. If you need to reference it, you can install the SQL MP and import only the library.

    Regards,


    Stoyan (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov


    Friday, November 3, 2017 9:05 AM
  • Thanks a lot Stoyan for your response.

    What <g class="gr_ gr_75 gr-alert gr_tiny gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace" data-gr-id="75" id="75">i</g> got from your response is that since we are planning to monitor our 2016 servers as well, so we would just need to add the 2016 MP <g class="gr_ gr_196 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace" data-gr-id="196" id="196">and than</g> import the library.MP from <g class="gr_ gr_331 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" data-gr-id="331" id="331">earlier</g> version to this new MP so that the same rule shall reference to 2016 servers as well. Is that <g class="gr_ gr_464 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" data-gr-id="464" id="464">correct ?</g>

    Since <g class="gr_ gr_437 gr-alert gr_tiny gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace" data-gr-id="437" id="437">i</g> am not that good at SCOM setup, to which 2016 MP will the library MP be imported <g class="gr_ gr_511 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace" data-gr-id="511" id="511">to</g>? any comments to this?

    Friday, November 3, 2017 12:30 PM
  • Hey,

    Each MP from Microsoft contains all the dependencies it needs, so that it can be installed successfully. You don't have to worry about dependenices in SCOM, the import wizard will do it for you.

    I will try to summarize this, assuming that with 2016 Servers you mean SQL Server 2016. It is pretty simple:

    - You download both Management Packs if you want to monitor SQL Server 2012 or older SQL versions - the one for SQL Server 2008, 2008 R2 and 2012:

    Microsoft System Center Management Pack for SQL Server

    and the one for SQL Server 2016:

    Microsoft System Center Management Pack for SQL Server 2016

    If you want to download only the SQL Server 2016 than you need only the SQL 2016 MP (the second link). You don't need libraries from previous versions. All the files you need are there after the install. 

    - You install both of the .msi files if you need SQL 2012 and older. You install only SQL MP for SQL Server 2016 if you want to monitor SQL Server 2016. This install is actuall only extracting the mp files onto the file system.

    - After you have installed (extracted them) you need to import the relevant MP files from the both installations.

    Important Note: Please import only the relevant MP files, not all. What I mean with this is that if you don't have SQL Always On availability groups or you don't have SQL Mirroring you don't need to import the respective MP files, like for example

    Microsoft.SQLServer.2008.Mirroring.Discovery.mp
    Microsoft.SQLServer.2008.Mirroring.Monitoring.mp
    Microsoft.SQLServer.2012.Mirroring.Discovery.mp
    Microsoft.SQLServer.2012.Mirroring.Monitoring.mp
    Microsoft.SQLServer.2012.AlwaysOn.Discovery.mp
    Microsoft.SQLServer.2012.AlwaysOn.Monitoring.mp

    So do import only the MPs for the scenarios you need.

    The same applyied for the SQL 2016. If you don't do Always On or Mirroring, don't import those:

    Microsoft.SQLServer.2016.Always On.Discovery.mp

    Microsoft.SQLServer.2016.Always On.Monitoring.mp

    Microsoft.SQLServer.2016.Always On.Views.mp

    Microsoft.SQLServer.2016.Mirroring.Discovery.mp

    Microsoft.SQLServer.2016.Mirroring.Monitoring.mp

    Microsoft.SQLServer.2016.Mirroring.Views.mp

    Import all the rest of the MPs.

    Don't worry about any dependenicies, the MP import wizard will let you know if something is missing, this is for sure.

    All of those MPs are sealed, this means you can reference and do overrides for each of the rules/monitors or comnfig settings within those management packs.

    Now to the OS monitoring: if you need to monitor Windows Serevr 2016, you need the WS 2016 Operating System MP:

    Microsoft System Center 2016 Management Pack for Windows Server Operating System

    If you are not familiar with the MP concepts (sealed, unsealed, referencing, etc.) I would strongly recommend, reading this:

    Management Packs: Guidelines and Best Practices

    and this one also:

    System Center Service Manager / Operations Manager Management Pack and Naming Convention Best Practices

    I hope I could explain this in an understandable manner. Ask you you will get answer, as always in this community :)

    Cheers,


    Stoyan (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov


    • Edited by Stoyan ChalakovMVP Friday, November 3, 2017 12:59 PM
    • Proposed as answer by Yan Li_ Monday, November 6, 2017 3:15 AM
    Friday, November 3, 2017 12:56 PM
  • Thanks Stoyan for your valuable details, appreciate your help.



    Monday, November 6, 2017 7:35 AM
  • Hello,

    As far as I know, you do not need to import Microsoft SQL Server Library management pack to monitor SQL 2016, just download them from the below link:

    https://www.microsoft.com/en-us/download/details.aspx?id=53008

    And import them into your management group. 

    As Stoyan replied, you do not need to import all of them, this depends on your requirements. 

    Regards,

    Yan Li


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

    • Proposed as answer by Yan Li_ Tuesday, November 7, 2017 6:24 AM
    Monday, November 6, 2017 8:14 AM
  • Thanks Yan for your response.

    From all the above discussion, it's clear that library MP is not required to monitor SQL server 2016 servers. so the rules tied up to this MP won't impact monitoring 2016 servers as it has a new set of MP. I hope that what we meant.

    Since we already have the library MP to monitor our existing 2012 and older servers. Wo would only be downloading the required MP for 2016 servers so that they can monitor new servers now. 

    • Proposed as answer by Yan Li_ Tuesday, November 7, 2017 6:24 AM
    Monday, November 6, 2017 9:54 AM
  • Hi there,

    "From all the above discussion, it's clear that library MP is not required to monitor SQL server 2016 servers. so the rules tied up to this MP won't impact monitoring 2016 servers as it has a new set of MP. I hope that what we meant." - Correct, the rule is targeted to OS versions other then WS 2016.

    "Since we already have the library MP to monitor our existing 2012 and older servers. Wo would only be downloading the required MP for 2016 servers so that they can monitor new servers now. " - also correct.

    Regards,


    Stoyan (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    • Proposed as answer by Yan Li_ Tuesday, November 7, 2017 6:24 AM
    Monday, November 6, 2017 10:07 AM