%3CLINGO-SUB%20id%3D%22lingo-sub-1603318%22%20slang%3D%22en-US%22%3EReleased%3A%20SQL%20Server%20Management%20Pack%20(7.0.24.0)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1603318%22%20slang%3D%22en-US%22%3E%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSPAN%3EAn%20updated%20version%20of%20SQL%20Server%20Management%20Pack%20is%20ready.%20It%20has%20many%20new%20features%20which%20are%20mostly%20based%20on%20your%20feedback.%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3EPlease%20download%20at%3A%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D56203%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20System%20Center%20Management%20Pack%20for%20SQL%20Server%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3E%3CSPAN%3EWhat%E2%80%99s%20New%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CP%3E%3CFONT%20size%3D%224%22%3EAdded%20a%20new%20%E2%80%9CSecurables%20Configuration%20Status%E2%80%9D%20monitor%20targeted%20to%20SQL%20Server%20databases%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CP%3E%3CFONT%20size%3D%224%22%3EUpdated%20the%20%E2%80%9CProduct%20Version%20Compliance%E2%80%9D%20monitor%20with%20the%20most%20recent%20versions%20of%20public%20updates%20for%20SQL%20Server%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CP%3E%3CFONT%20size%3D%224%22%3EUpdated%20the%20%E2%80%9CSecurables%20Configuration%20Status%E2%80%9D%20monitor%20targeted%20to%20the%20DB%20Engine%20when%20a%20SQL%20Server%20instance%20participates%20in%20Availability%20Groups%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CP%3E%3CFONT%20size%3D%224%22%3ERemoved%20the%20%E2%80%9CSecurables%20Configuration%20Status%E2%80%9D%20monitor%20targeted%20to%20the%20Availability%20Replica%20as%20non-useful%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CP%3E%3CFONT%20size%3D%224%22%3EUpdated%20the%20%E2%80%9CSQL%20Server%20Database%20Engines%E2%80%9D%20discovery%3B%20the%20%E2%80%9CNetbios%20Computer%20Name%E2%80%9D%20property%20is%20now%20uppercased.%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EAdded%20reports%20from%20version-specific%20management%20packs%20for%20SQL%20Server%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EUpdated%20monitor%20%E2%80%9CJob%20Duration%E2%80%9D%20to%20add%20current%20job%20run's%20duration%20to%20its%20alert%20description%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EUpdated%20Web%20Console%20version%20of%20SQL%20MP%20Dashboards%20to%20support%20SCOM%202019%20UR1%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EUpdated%20alert%20description%20of%20monitor%20%E2%80%9CSecurables%20Configuration%20Status%E2%80%9D%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EAdded%20%E2%80%9CCheckStartupType%E2%80%9D%20property%20to%20SSIS%20Health%20Status%20monitor%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3ERevised%20columns%20of%20SQL%20Agent%20and%20SQL%20Agent%20Jobs%20state%20views%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EUpdated%20display%20strings%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EIssues%20Fixed%3C%2FFONT%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EFixed%20error%20%E2%80%9CUnsupported%20path%20format%E2%80%9D%20in%20workflows%20targeting%20Filegroups%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EFixed%20discovery%20error%20on%20non-readable%20availability%20replicas%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EFixed%20wrong%20Run%20As%20profile%20in%20SSIS%20Seed%20Discovery%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EFixed%20issue%20that%20caused%20rule%20%E2%80%9CDisable%20Discovery%20of%20Selected%20DB%20Engines%E2%80%9D%20to%20fail%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EFixed%20discovery%20issue%20for%20databases%20in%20recovering%20state%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EFixed%20issue%20in%20monitor%20%E2%80%9CSecurables%20Configuration%20Status%E2%80%9D%20when%20it%20went%20critical%20on%20Shared-Memory-only%20SQL%20Servers%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CP%3E%3CFONT%20size%3D%224%22%3EFixed%20the%20Alerting%20Rules%20data%20source%20to%20avoid%20an%20alert%20storm%20after%20exiting%20maintenance%20mode%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CP%3E%3CFONT%20size%3D%224%22%3EFixed%20the%20SQL%20Log%20Reader%20data%20source%20to%20support%20changing%20of%20the%20SQL%20Authentication%20method%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CP%3E%3CFONT%20size%3D%224%22%3EFixed%20the%20Performance%20Reader%20data%20source%20to%20support%20changing%20of%20the%20SQL%20Authentication%20method%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3EFixed%20issue%20in%20data%20source%20of%20SPN%20Status%20monitor%20that%20may%20lead%20to%20memory%20leak%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3EWe%20are%20looking%20forward%20to%20hearing%20your%20feedback.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1603318%22%20slang%3D%22en-US%22%3E%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSPAN%3EAn%20updated%20version%20of%20SQL%20Server%20Management%20Pack%20is%20ready.%20It%20has%20many%20new%20features%20which%20are%20mostly%20based%20on%20your%20feedback.%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1603318%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESQLReleases%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1645935%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20SQL%20Server%20Management%20Pack%20(7.0.24.0)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1645935%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20%22Long%20Running%20Jobs%22%20monitor%20often%20had%20false%20positives%20whenever%20the%20SQL%20Agent%20is%20restarted.%26nbsp%3B%20On%20this%20monitor's%20SQL%20query%20can%20you%20please%20join%20in%20the%20Agent's%20start%20date%20as%20described%20in%20here%3F%20%3CA%20href%3D%22https%3A%2F%2Fdba.stackexchange.com%2Fquestions%2F63349%2Foprhaned-entries-in-msdb-sysjobactivity%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdba.stackexchange.com%2Fquestions%2F63349%2Foprhaned-entries-in-msdb-sysjobactivity%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1796225%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20SQL%20Server%20Management%20Pack%20(7.0.24.0)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1796225%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F786309%22%20target%3D%22_blank%22%3E%40RMacN1295%3C%2FA%3E%26nbsp%3B%2C%26nbsp%3B%3CSPAN%3Ethanks%20for%20reaching%20us%20out!%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EWe%E2%80%99ll%20put%20this%20item%20in%20our%20backlog%20for%20the%20next%20release%2C%20but%20no%20more%20precise%20ETA%20yet%20though.%3C%2FP%3E%3CP%3EWe%20look%20forward%20to%20hearing%20your%20feedback%20in%20the%20future.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

An updated version of SQL Server Management Pack is ready. It has many new features which are mostly based on your feedback.

 

Please download at:

Microsoft System Center Management Pack for SQL Server

 

What’s New

  • Added a new “Securables Configuration Status” monitor targeted to SQL Server databases

  • Updated the “Product Version Compliance” monitor with the most recent versions of public updates for SQL Server

  • Updated the “Securables Configuration Status” monitor targeted to the DB Engine when a SQL Server instance participates in Availability Groups

  • Removed the “Securables Configuration Status” monitor targeted to the Availability Replica as non-useful

  • Updated the “SQL Server Database Engines” discovery; the “Netbios Computer Name” property is now uppercased.

  • Added reports from version-specific management packs for SQL Server
  • Updated monitor “Job Duration” to add current job run's duration to its alert description
  • Updated Web Console version of SQL MP Dashboards to support SCOM 2019 UR1
  • Updated alert description of monitor “Securables Configuration Status”
  • Added “CheckStartupType” property to SSIS Health Status monitor
  • Revised columns of SQL Agent and SQL Agent Jobs state views
  • Updated display strings

Issues Fixed

  • Fixed error “Unsupported path format” in workflows targeting Filegroups
  • Fixed discovery error on non-readable availability replicas
  • Fixed wrong Run As profile in SSIS Seed Discovery
  • Fixed issue that caused rule “Disable Discovery of Selected DB Engines” to fail
  • Fixed discovery issue for databases in recovering state
  • Fixed issue in monitor “Securables Configuration Status” when it went critical on Shared-Memory-only SQL Servers
  • Fixed the Alerting Rules data source to avoid an alert storm after exiting maintenance mode

  • Fixed the SQL Log Reader data source to support changing of the SQL Authentication method

  • Fixed the Performance Reader data source to support changing of the SQL Authentication method

  • Fixed issue in data source of SPN Status monitor that may lead to memory leak

We are looking forward to hearing your feedback.

 

2 Comments
Occasional Visitor

The "Long Running Jobs" monitor often had false positives whenever the SQL Agent is restarted.  On this monitor's SQL query can you please join in the Agent's start date as described in here? https://dba.stackexchange.com/questions/63349/oprhaned-entries-in-msdb-sysjobactivity

 

Thank you!

Senior Member

Hello @RMacN1295 , thanks for reaching us out!

We’ll put this item in our backlog for the next release, but no more precise ETA yet though.

We look forward to hearing your feedback in the future.