Blog Post

SQL Server Blog
2 MIN READ

Released: Public Preview for SQL Server Management Pack (2012-2019)

EbruErsan's avatar
EbruErsan
Icon for Microsoft rankMicrosoft
Nov 25, 2019

We are getting ready to release a new version of SQL Server Management Pack. Please install and use this public preview and send us your feedback (sqlmpsfeedback@microsoft.com)! We appreciate the time and effort you spend on these previews which make the final product so much better.

 

Please download at:

Microsoft System Center Management Pack (Community Technology Preview) for SQL Server

 

New features and fixes in this version (7.0.18.0):

  • Updated MP to support SQL Server 2019 RTM
  • Added filter by edition to “Local DB Engine Discovery”
  • Redesigned DB Space monitoring to improve performance: Enabled by default monitors and performance rules targeting Database which watch for disk space consumption by ROWS filegroups and Logfiles
  • Redesigned DB Space monitoring: Added two monitors and two performance rules to watch for disk space consumption by In-Memory and FILESTREAM data at the Database level
  • Redesigned DB Space monitoring: Disabled by default all workflows targeting Filegroups, Files, Logfiles
  • Added attribute “TCP Port” to “SQL DB Engine Class” and updated “DB Engine Discovery” to populate the new property
  • Added summary dashboard for SCOM 2019 Web Console (HTML5)
  • Added support for cluster nodes with disjoined namespaces
  • Updated alert descriptions of monitors “Availability Database,” “Availability Replica,” and “Availability Group” (generating alerts still disabled by default)
  • Updated monitor “Product Version Compliance” with versions of most recent public updates to SQL Server
  • Disabled by default monitor “Buffer Cache Hit Ratio” and changed its threshold from 0% to 90%
  • Disabled by default monitor “Page Life Expectancy”
  • Removed monitors “Availability Database Join State” and “Availability Replica Join State” as not useful
  • Updated display strings
  • Revised columns on DB Engine state views
  • Fixed: monitor “Service Principal Name Configuration Status” raises false alerts because of case-sensitive comparison
  • Fixed: “Local DB Engine Discovery” crashes when Windows has Turkish locale
  • Fixed issue that caused performance degradation in workflows “General Always On Discovery,” “Database Replica Discovery,” and “Always On System Policy Monitoring”
  • Fixed: “General Always On Discovery” throws errors on environments with several Distributed Availability Groups
  • Fixed monitoring issue in case of Database is replicated by Always On Availability Group
  • Fixed empty property bag when Availability Group has cluster type NONE
  • Fixed wrong target in alerting rule “DB Backup Failed to Complete”
  • Fixed rule “MSSQL Integration Services on Windows: The package restarted from checkpoint file” and its alert
  • Fixed rule “OS Error occurred while performing I/O on pages“ and its alert
  • Fixed: "DB Disk Write Latency" and "DB Disk Read Latency" monitors and performance rules get wrong performance metric

We are looking forward to hearing your feedback.

 

Published Nov 25, 2019
Version 1.0

4 Comments

  • DVKalashnikov's avatar
    DVKalashnikov
    Brass Contributor

    Hello Igor888888 

    Thanks for reaching us out! At the moment, we don't have any ETA for this performance optimization, and the next RTM build which will be released in late December, will also not have this optimization. But we have this in our backlog and we'll do our best to present it in the next year!

  • Igor888888's avatar
    Igor888888
    Copper Contributor

    Well i cant see any errors. Are there any ETA for rules performance optimization enabled ?

     

     

  • DVKalashnikov's avatar
    DVKalashnikov
    Brass Contributor

    Hello smilne

    Thank you for your feedback and the following proposal! I've added this to our backlog for further investigation.

    Btw, for more convenient communication you can reach us out via this support address: mailto:sqlmpsfeedback@microsoft.com

  • smilne's avatar
    smilne
    Copper Contributor

    Crossposting from UserVoice:

     

    When the Version Agnostic management pack attempts to collect VLF counts, it uses DBCC LOGINFO("dbname") to achieve this. Would it be possible to update this workflow to use sys.dm_db_log_info instead? This replaces DBCC LOGINFO as described in the below documentation:

    https://docs.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-db-log-info-transact-sql?view=sql-server-ver15#remarks

     

    DBCC LOGINFO("model")

    User 'DOMAIN\AgentAccount' does not have permission to run DBCC LOGINFO.

     

    https://systemcenterom.uservoice.com/forums/293064-general-operations-manager-feedback/suggestions/39146965-update-db-virtual-log-file-workflow-to-use-sys-dm