Home
%3CLINGO-SUB%20id%3D%22lingo-sub-479573%22%20slang%3D%22en-US%22%3EReleased%3A%20Version-agnostic%20Management%20Pack%20for%20SQL%20Server%20(7.0.15.0)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-479573%22%20slang%3D%22en-US%22%3E%3CH4%20id%3D%22toc-hId-1315550233%22%20id%3D%22toc-hId-1315550235%22%20id%3D%22toc-hId-1315550235%22%20id%3D%22toc-hId-1315550235%22%20id%3D%22toc-hId-1315550235%22%20id%3D%22toc-hId-1315550235%22%20id%3D%22toc-hId-1315550235%22%20id%3D%22toc-hId-1315550235%22%20id%3D%22toc-hId-1315550235%22%20id%3D%22toc-hId-1315550235%22%20id%3D%22toc-hId-1315550235%22%3EVersion-agnostic%20management%20pack%20for%20SQL%20Server%20now%20supports%20SQL%20Server%202012%2C%202014%2C%20and%202016%20in%20addition%20to%202017%20and%20up%3C%2FH4%3E%0A%3CP%3EThis%20management%20pack%20is%20virtually%20a%20new%20version%20of%20the%20version-agnostic%20management%20pack%20for%20SQL%20Server%202017%20and%20up%2C%20whose%20last%20version%2C%207.0.7.0%2C%20was%20released%20in%20July%202018.%20This%20update%20allows%20the%20management%20pack%20to%20monitor%20SQL%20Server%202012%2C%202014%2C%20and%202016%20in%20addition%20to%20previously%20supported%202017%20and%20up.%20The%20former%20generation%20of%20management%20packs%20for%20SQL%20Server%202008-2016%20has%20reached%20the%20end%20of%20support%20with%20this%20release%20as%20we%20have%20announced%20previously%20(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSQL-Server%2FReleased-System-Center-Management-Packs-for-SQL-Server-2008-2016%2Fba-p%2F391179%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eblog%20post%3C%2FA%3E).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%20also%20releasing%20new%20versions%20(7.0.15.0)%20of%20SQL%20Server%202017%2B%20Replication%20and%20SQL%20Server%202017%2B%20Reporting%20Services%20management%20packs%20compatible%20with%20this%20new%20version-agnostic%20SQL%20Server%20management%20pack.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDownloads%20available%20at%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.microsoft.com%252Fen-us%252Fdownload%252Fdetails.aspx%253Fid%253D56203%26amp%3Bdata%3D02%257C01%257CEbru.Ersan%2540microsoft.com%257C838270be8b89471c4f4e08d6c71182c1%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C636915275371770151%26amp%3Bsdata%3DcatY6%252Fbtn9SqzIOhctwBQSiJ8sFLdh3NpPgv36EVCQ4%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20System%20Center%20Management%20Pack%20for%20SQL%20Server%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D56204%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20System%20Center%20Management%20Pack%20for%20SQL%20Server%202017%2B%20Replication%20%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D57381%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20System%20Center%20Management%20Pack%20for%20SQL%20Server%202017%2B%20Reporting%20Services%20%3C%2FA%3E%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId--1236606728%22%20id%3D%22toc-hId--1236606726%22%20id%3D%22toc-hId--1236606726%22%20id%3D%22toc-hId--1236606726%22%20id%3D%22toc-hId--1236606726%22%20id%3D%22toc-hId--1236606726%22%20id%3D%22toc-hId--1236606726%22%20id%3D%22toc-hId--1236606726%22%20id%3D%22toc-hId--1236606726%22%20id%3D%22toc-hId--1236606726%22%20id%3D%22toc-hId--1236606726%22%3E%26nbsp%3B%3C%2FH4%3E%0A%3CH4%20id%3D%22toc-hId-506203607%22%20id%3D%22toc-hId-506203609%22%20id%3D%22toc-hId-506203609%22%20id%3D%22toc-hId-506203609%22%20id%3D%22toc-hId-506203609%22%20id%3D%22toc-hId-506203609%22%20id%3D%22toc-hId-506203609%22%20id%3D%22toc-hId-506203609%22%20id%3D%22toc-hId-506203609%22%20id%3D%22toc-hId-506203609%22%20id%3D%22toc-hId-506203609%22%3EBenefits%20of%20single%20version-agnostic%20SQL%20Server%20MP%3C%2FH4%3E%0A%3CUL%3E%0A%3CLI%3EEasier%20MP%20management%20with%20a%20single%20MP%20to%20monitor%20all%20SQL%20Server%20versions.%3C%2FLI%3E%0A%3CLI%3EEasier%20to%20develop%20and%20maintain%20custom%20developed%20solutions%20based%20on%20SQL%20Server%20MP.%20You%20will%20be%20able%20to%20create%20a%20single%20solution%20for%20all%20the%20versions%20of%20SQL%20Server%20instead%20of%20being%20forced%20to%20have%20four%20different%20solutions%20like%20today%20(2008-2012%2C%202014%2C%202016%2C%202017).%3C%2FLI%3E%0A%3CLI%3EAgentless%20monitoring%20available%20for%20the%20older%20versions%20of%20SQL%20Server.%3C%2FLI%3E%0A%3CLI%3ESimplified%20Run%20As%20configuration%20-%20one%20set%20of%20Run%20As%20profiles%20shared%20across%20all%20version-agnostic%20MPs.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId--2045953354%22%20id%3D%22toc-hId--2045953352%22%20id%3D%22toc-hId--2045953352%22%20id%3D%22toc-hId--2045953352%22%20id%3D%22toc-hId--2045953352%22%20id%3D%22toc-hId--2045953352%22%20id%3D%22toc-hId--2045953352%22%20id%3D%22toc-hId--2045953352%22%20id%3D%22toc-hId--2045953352%22%20id%3D%22toc-hId--2045953352%22%20id%3D%22toc-hId--2045953352%22%3EUpgradability%20issues%3C%2FH4%3E%0A%3CP%3EThis%20version-agnostic%20SQL%20Server%20MP%20is%20significantly%20different%20than%20the%20SQL%20Server%202017%2B%20MP.%20This%20means%20that%20there%20are%20some%20upgrade%20issues%20you%20need%20to%20be%20aware%20of%20and%20take%20action%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EAfter%20importing%20this%20management%20pack%20over%20the%20SQL%20Server%202017%2B%20MP%2C%20all%20already-discovered%20instances%20of%20SQL%20Server%202017%20will%20be%20re-discovered.%20This%20will%20cause%20SCOM%20to%20%E2%80%9Cforget%E2%80%9D%20historical%20data%20for%20these%20instances%2C%20which%20will%20affect%20reporting.%3C%2FLI%3E%0A%3CLI%3EManagement%20pack%20for%20SQL%20Server%202017%2B%20Integration%20Services%20cannot%20be%20upgraded%20and%20has%20to%20be%20removed%20before%20importing%20this%20update.%20Remove%20the%20following%20management%20pack%20(this%20file%20is%20part%20of%20the%20delivery%20of%20SQL%20Server%202017%2B%20MP)%3A%20Microsoft%20SQL%20Server%202017%2B%20Integration%20Services%20on%20Windows%3C%2FLI%3E%0A%3CLI%3EMonitoring%20management%20pack%20for%20SQL%20Server%202017%2B%20Replication%20cannot%20be%20upgraded%20and%20has%20to%20be%20removed%20before%20importing%20this%20update.%20Remove%20the%20following%20management%20pack%20(this%20file%20is%20part%20of%20the%20delivery%20of%20SQL%20Server%202017%2B%20Replication%20MP)%3A%20Microsoft%20SQL%20Server%202017%2B%20on%20Windows%20Replication%20(Monitoring)%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CH4%20id%3D%22toc-hId--303143019%22%20id%3D%22toc-hId--303143017%22%20id%3D%22toc-hId--303143017%22%20id%3D%22toc-hId--303143017%22%20id%3D%22toc-hId--303143017%22%20id%3D%22toc-hId--303143017%22%20id%3D%22toc-hId--303143017%22%20id%3D%22toc-hId--303143017%22%20id%3D%22toc-hId--303143017%22%20id%3D%22toc-hId--303143017%22%20id%3D%22toc-hId--303143017%22%3E%26nbsp%3B%3C%2FH4%3E%0A%3CH4%20id%3D%22toc-hId-1439667316%22%20id%3D%22toc-hId-1439667318%22%20id%3D%22toc-hId-1439667318%22%20id%3D%22toc-hId-1439667318%22%20id%3D%22toc-hId-1439667318%22%20id%3D%22toc-hId-1439667318%22%20id%3D%22toc-hId-1439667318%22%20id%3D%22toc-hId-1439667318%22%20id%3D%22toc-hId-1439667318%22%20id%3D%22toc-hId-1439667318%22%20id%3D%22toc-hId-1439667318%22%3ELocalization%20for%20SQL%20Server%202017%2B%20MP%20cannot%20be%20imported%20over%20the%20current%20version%20of%20SQL%20Server%20MP%3C%2FH4%3E%0A%3CP%3EThis%20management%20pack%20cannot%20be%20localized%20with%20the%20localization%20packs%20initially%20made%20for%20SQL%20Server%202017%2B%20MP.%20If%20you%20already%20have%20SQL%20Server%202017%2B%20MP%20(7.0.0.0%20or%207.0.7.0)%20imported%20and%20localized%2C%20then%20you%20do%20not%20need%20to%20remove%20the%20localization%20pack%20before%20importing%20the%20new%20version-agnostic%20management%20pack.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId--1112489645%22%20id%3D%22toc-hId--1112489643%22%20id%3D%22toc-hId--1112489643%22%20id%3D%22toc-hId--1112489643%22%20id%3D%22toc-hId--1112489643%22%20id%3D%22toc-hId--1112489643%22%20id%3D%22toc-hId--1112489643%22%20id%3D%22toc-hId--1112489643%22%20id%3D%22toc-hId--1112489643%22%20id%3D%22toc-hId--1112489643%22%20id%3D%22toc-hId--1112489643%22%3ESQL%20Server%20MP%20Changelog%3C%2FH4%3E%0A%3CUL%3E%0A%3CLI%3EUpdated%20MP%20to%20support%20SQL%20Server%202019%20(verified%20with%20CTP%20version%202.4)%3C%2FLI%3E%0A%3CLI%3EAdded%20support%20for%20computers%20with%20the%20same%20NetBIOS%20computer%20name%20placed%20in%20different%20domains%3C%2FLI%3E%0A%3CLI%3EUpdated%20%E2%80%9CProduct%20Version%20Compliance%E2%80%9D%20monitor%20to%20check%20instances%20of%20SQL%20Server%202012%20and%20higher%3C%2FLI%3E%0A%3CLI%3EUpdated%20%E2%80%9CDatabase%20Log%20Backup%20Status%E2%80%9D%20monitor%20to%20consider%20SIMPLE%20recovery%20model%3C%2FLI%3E%0A%3CLI%3EUpdated%20SQL%20DB%20Engine%20class%3A%20Added%20%E2%80%9CNetBIOS%20Domain%20name%E2%80%9D%20property%3C%2FLI%3E%0A%3CLI%3EUpdated%20%E2%80%9CProduct%20Version%20Compliance%E2%80%9D%20monitor%20to%20set%20SQL%20Server%202017%20CU14%20as%20minimal%20version%3C%2FLI%3E%0A%3CLI%3EUpdated%20%E2%80%9CService%20Principal%20Name%20Configuration%20Status%E2%80%9D%20monitor%20and%20%E2%80%9CLogin%20failed%E2%80%9D%20and%20%E2%80%9CDatabase%20consistency%20check%20performed%20with%20no%20errors%E2%80%9D%20alerting%20rules%20to%20disable%20them%20by%20default%3C%2FLI%3E%0A%3CLI%3EAdded%20rule%20that%20turns%20on%20maintenance%20mode%20for%20certain%20instances%20of%20SQL%20Server%20MP%20objects%20when%20hosting%20computer%20is%20sent%20to%20maintenance%3C%2FLI%3E%0A%3CLI%3EUpdated%20%E2%80%9CTransaction%20Log%20Free%20Space%E2%80%9D%20monitor%20to%20show%20free%20space%20in%20percent%20value%20in%20its%20alerts%3C%2FLI%3E%0A%3CLI%3EUpdated%20display%20strings%3C%2FLI%3E%0A%3CLI%3EBrought%20back%20%E2%80%9CIS%20Views%E2%80%9D%20file%20in%20MSI%20package%3C%2FLI%3E%0A%3CLI%3EFixed%3A%20%E2%80%9CBuffer%20Cache%20Hit%20Ratio%E2%80%9D%20performance%20rule%20and%20monitor%20get%20values%20greater%20100%25%3C%2FLI%3E%0A%3CLI%3EFixed%3A%20%E2%80%9CAvailability%20Group%20Online%20(rollup)%E2%80%9D%20monitor%20raises%20alerts%20with%20not%20replaced%20placeholders%3C%2FLI%3E%0A%3CLI%3EFixed%20exception%20treating%20in%20%E2%80%9CResource%20Pool%20Memory%20Consumption%E2%80%9D%20monitor%3C%2FLI%3E%0A%3CLI%3EFixed%3A%20%E2%80%9CService%20Principal%20Name%20Configuration%20Status%E2%80%9D%20monitor%20raises%20false%20alerts%20because%20of%20case-sensitive%20comparison%3C%2FLI%3E%0A%3CLI%3EFixed%3A%20%E2%80%9CIntegration%20Services%20Seed%E2%80%9D%20discovery%20throws%20errors%20on%20cluster%20nodes%3C%2FLI%3E%0A%3CLI%3EFixed%20event%20log%20category%20for%20%E2%80%9CDB%20Engine%20Seed%E2%80%9D%20discovery%3C%2FLI%3E%0A%3CLI%3EFixed%20alert%20message%20in%20%E2%80%9CMemory-Optimized%20Data%20Stale%20Checkpoint%20File%20Pairs%20Ratio%E2%80%9D%20monitor%3C%2FLI%3E%0A%3CLI%3EFixed%20issues%20in%20cookdown%20of%20%E2%80%9CUser%20Policy%E2%80%9D%20and%20%E2%80%9CGeneral%20Always%20On%E2%80%9D%20discoveries%20that%20caused%20performance%20degradation%20in%20workflows%3C%2FLI%3E%0A%3CLI%3EFixed%3A%20%E2%80%9CService%20Principal%20Name%20Configuration%20Status%E2%80%9D%20monitor%20throws%20errors%20when%20computer%20is%20not%20domain-joined%3C%2FLI%3E%0A%3CLI%3EFixed%20%E2%80%9CDatabase%20Log%20Backup%20Status%E2%80%9D%20monitor%20for%20SQL%20Server%20for%20Linux%3C%2FLI%3E%0A%3CLI%3EFixed%20list%20of%20required%20permissions%20for%20SQL%20Server%202012%20in%20%E2%80%9CSecurables%20Configuration%20Status%E2%80%9D%20monitor%3C%2FLI%3E%0A%3CLI%3EFixed%3A%20%E2%80%9CDatabase%20User%20Policy%E2%80%9D%20discovery%20failures%20for%20AG%20secondary%20replica%3C%2FLI%3E%0A%3CLI%3EFixed%20event%20log%20source%20description%20of%20%E2%80%9CVLF%20Count%E2%80%9D%20performance%20rule%20for%20SQL%20Server%20on%20Linux%3C%2FLI%3E%0A%3CLI%3EFixed%20performance%20rules%20for%20SQL%20Server%202017%20Integration%20Services%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId-630320690%22%20id%3D%22toc-hId-630320692%22%20id%3D%22toc-hId-630320692%22%20id%3D%22toc-hId-630320692%22%20id%3D%22toc-hId-630320692%22%20id%3D%22toc-hId-630320692%22%20id%3D%22toc-hId-630320692%22%20id%3D%22toc-hId-630320692%22%20id%3D%22toc-hId-630320692%22%20id%3D%22toc-hId-630320692%22%20id%3D%22toc-hId-630320692%22%3ESQL%20Server%202017%2B%20Replication%20MP%20Changelog%3C%2FH4%3E%0A%3CUL%3E%0A%3CLI%3ESupported%20last%20changes%20in%20version-agnostic%20management%20pack%20for%20SQL%20Server%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId--1921836271%22%20id%3D%22toc-hId--1921836269%22%20id%3D%22toc-hId--1921836269%22%20id%3D%22toc-hId--1921836269%22%20id%3D%22toc-hId--1921836269%22%20id%3D%22toc-hId--1921836269%22%20id%3D%22toc-hId--1921836269%22%20id%3D%22toc-hId--1921836269%22%20id%3D%22toc-hId--1921836269%22%20id%3D%22toc-hId--1921836269%22%20id%3D%22toc-hId--1921836269%22%3ESQL%20Server%202017%2B%20Reporting%20Services%20MP%20Changelog%3C%2FH4%3E%0A%3CUL%3E%0A%3CLI%3ESupported%20last%20changes%20in%20version-agnostic%20management%20pack%20for%20SQL%20Server%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-479573%22%20slang%3D%22en-US%22%3E%3CP%3EVersion-agnostic%20management%20pack%20for%20SQL%20Server%20now%20supports%20SQL%20Server%202012%2C%202014%2C%20and%202016%20in%20addition%20to%202017%20and%20up.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480154%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20Version-agnostic%20Management%20Pack%20for%20SQL%20Server%20(7.0.15.0)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480154%22%20slang%3D%22en-US%22%3E%3CP%3EThanks.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22http%3A%2F%2Ftourcalm.com%2Fqom%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%D9%82%D9%85%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481456%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20Version-agnostic%20Management%20Pack%20for%20SQL%20Server%20(7.0.15.0)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481456%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20to%20see!%3C%2FP%3E%3CP%3EA%20few%20questions%2C%20though%3A%3C%2FP%3E%3CP%3E1)%20Is%20there%20a%20plan%20to%20update%20the%20SQL%20Server%20Dashboards%20to%20work%20with%20the%20new%20HTML5%20web%20console%3F%3C%2FP%3E%3CP%3E2)%20Will%20the%20Analysis%20Sevices%2C%20Reporting%20Services%2C%20and%20Replication%20packs%20be%20updated%20to%20accommodate%20the%20new%20version%20agnostic%20MPs%3F%20Or%20better%20still%2C%20included%20with%20the%20new%20MPs%3F%3C%2FP%3E%3CP%3E3)%20Would%20it%20be%20possible%20to%20get%20an%20update%20SQLServerMPWorkflowList.pdf%3F%26nbsp%3B%20This%20is%20very%20useful%20to%20be%20able%20to%20provide%20to%20my%20DBAs%20in%20order%20to%20ensure%20that%20they%20are%20getting%20exactly%20what%20they%20want%20monitored.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-503020%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20Version-agnostic%20Management%20Pack%20for%20SQL%20Server%20(7.0.15.0)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-503020%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F325178%22%20target%3D%22_blank%22%3E%40mkmaster78%3C%2FA%3E%26nbsp%3Bthank%20you%20for%20your%20questions.%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EWe're%20currently%20working%20on%20creating%20an%20HTML5%20version%20of%20SQL%20Server%20Dashboards.%20There's%20no%20precise%20plan%20yet%2C%20the%20feature%20will%20be%20introduced%20in%20one%20of%20the%20upcoming%20releases.%3C%2FLI%3E%0A%3CLI%3EWe%20don%E2%80%99t%20have%20anything%20to%20announce%20here%20yet.%3C%2FLI%3E%0A%3CLI%3EThe%20download%20page%20has%20been%20updated.%20You%20can%20now%20download%20the%20workflow%20list.%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-655084%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20Version-agnostic%20Management%20Pack%20for%20SQL%20Server%20(7.0.15.0)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-655084%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20installed%20the%20version%20MPs%202008%2C2012%2C2014%2C2016.%20Should%20I%20remove%20the%202014-2016%20MP%3As%20when%20installing%20this%20one%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-657860%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20Version-agnostic%20Management%20Pack%20for%20SQL%20Server%20(7.0.15.0)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-657860%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F351138%22%20target%3D%22_blank%22%3E%40Jannep%3C%2FA%3E%26nbsp%3Bwhen%20you%20install%20the%20version-agnostic%20management%20pack%20on%20SCOM%20where%20there%20already%20are%20the%20version-specific%20MPs%20for%20SQL%202008-2016%2C%20the%20new%20management%20pack%20won't%20discover%20and%20monitor%20SQL%202012-2016%20by%20default.%20It%20was%20made%20to%20avoid%20double%20monitoring.%20If%20you%20want%20to%20monitor%20SQL%202012-2016%20with%20the%20new%20management%20pack%2C%20you%20can%20either%20remove%20the%20version-specific%20management%20packs%20before%20importing%20the%20new%20one%20or%2C%20if%20you%20have%20already%20imported%20it%2C%20override%20the%20DB%20Engine%20discovery%20so%20it%20begins%20to%20discover%20SQL%202008-2016.%20Also%2C%20in%20the%20latter%20case%2C%20it's%20up%20to%20you%20when%20to%20remove%20the%20version-specific%20MPs%20-%20before%20or%20after%20enabling%20the%20new%20MP%20to%20discover%20SQL%202012-2016.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHow%20to%20enable%20the%20monitoring%20of%20SQL%202012-2016%20is%20described%20in%20the%20operations%20guide%20to%20this%20management%20pack%20in%20the%20section%20%22Turning%20on%20the%20monitoring%20of%20SQL%20Server%202012-2016.%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-890861%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20Version-agnostic%20Management%20Pack%20for%20SQL%20Server%20(7.0.15.0)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-890861%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20wondering%20why%20the%20%22Tcp%20Port%22%20property%20of%20the%20Database%20Engines%20is%20not%20included%20in%20this%20management%20pack%2C%20whereas%20it%20was%20in%20the%20version-specific%20management%20packs.%26nbsp%3B%20Having%20this%20available%20for%20inventory%2Fgeneral%20info%20is%20very%20important%20to%20our%20DBA'a%20and%20they%20are%20quite%20upset%20to%20see%20it%20missing.%26nbsp%3B%20Hopefully%20it%20can%20be%20added%20back%20in%20a%20future%20update...%3F%26nbsp%3B%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-892842%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20Version-agnostic%20Management%20Pack%20for%20SQL%20Server%20(7.0.15.0)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-892842%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20feedback.%20This%20is%20a%20popular%20ask.%20The%20plan%20is%20to%20introduce%20it%20back%20in%20the%20next%20update%20(no%20timeline%20to%20share%20yet).%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Version-agnostic management pack for SQL Server now supports SQL Server 2012, 2014, and 2016 in addition to 2017 and up

This management pack is virtually a new version of the version-agnostic management pack for SQL Server 2017 and up, whose last version, 7.0.7.0, was released in July 2018. This update allows the management pack to monitor SQL Server 2012, 2014, and 2016 in addition to previously supported 2017 and up. The former generation of management packs for SQL Server 2008-2016 has reached the end of support with this release as we have announced previously (blog post).

 

We are also releasing new versions (7.0.15.0) of SQL Server 2017+ Replication and SQL Server 2017+ Reporting Services management packs compatible with this new version-agnostic SQL Server management pack.

 

Downloads available at:

Microsoft System Center Management Pack for SQL Server

Microsoft System Center Management Pack for SQL Server 2017+ Replication

Microsoft System Center Management Pack for SQL Server 2017+ Reporting Services

 

Benefits of single version-agnostic SQL Server MP

  • Easier MP management with a single MP to monitor all SQL Server versions.
  • Easier to develop and maintain custom developed solutions based on SQL Server MP. You will be able to create a single solution for all the versions of SQL Server instead of being forced to have four different solutions like today (2008-2012, 2014, 2016, 2017).
  • Agentless monitoring available for the older versions of SQL Server.
  • Simplified Run As configuration - one set of Run As profiles shared across all version-agnostic MPs.

 

Upgradability issues

This version-agnostic SQL Server MP is significantly different than the SQL Server 2017+ MP. This means that there are some upgrade issues you need to be aware of and take action:

 

  • After importing this management pack over the SQL Server 2017+ MP, all already-discovered instances of SQL Server 2017 will be re-discovered. This will cause SCOM to “forget” historical data for these instances, which will affect reporting.
  • Management pack for SQL Server 2017+ Integration Services cannot be upgraded and has to be removed before importing this update. Remove the following management pack (this file is part of the delivery of SQL Server 2017+ MP): Microsoft SQL Server 2017+ Integration Services on Windows
  • Monitoring management pack for SQL Server 2017+ Replication cannot be upgraded and has to be removed before importing this update. Remove the following management pack (this file is part of the delivery of SQL Server 2017+ Replication MP): Microsoft SQL Server 2017+ on Windows Replication (Monitoring)

 

Localization for SQL Server 2017+ MP cannot be imported over the current version of SQL Server MP

This management pack cannot be localized with the localization packs initially made for SQL Server 2017+ MP. If you already have SQL Server 2017+ MP (7.0.0.0 or 7.0.7.0) imported and localized, then you do not need to remove the localization pack before importing the new version-agnostic management pack.

 

SQL Server MP Changelog

  • Updated MP to support SQL Server 2019 (verified with CTP version 2.4)
  • Added support for computers with the same NetBIOS computer name placed in different domains
  • Updated “Product Version Compliance” monitor to check instances of SQL Server 2012 and higher
  • Updated “Database Log Backup Status” monitor to consider SIMPLE recovery model
  • Updated SQL DB Engine class: Added “NetBIOS Domain name” property
  • Updated “Product Version Compliance” monitor to set SQL Server 2017 CU14 as minimal version
  • Updated “Service Principal Name Configuration Status” monitor and “Login failed” and “Database consistency check performed with no errors” alerting rules to disable them by default
  • Added rule that turns on maintenance mode for certain instances of SQL Server MP objects when hosting computer is sent to maintenance
  • Updated “Transaction Log Free Space” monitor to show free space in percent value in its alerts
  • Updated display strings
  • Brought back “IS Views” file in MSI package
  • Fixed: “Buffer Cache Hit Ratio” performance rule and monitor get values greater 100%
  • Fixed: “Availability Group Online (rollup)” monitor raises alerts with not replaced placeholders
  • Fixed exception treating in “Resource Pool Memory Consumption” monitor
  • Fixed: “Service Principal Name Configuration Status” monitor raises false alerts because of case-sensitive comparison
  • Fixed: “Integration Services Seed” discovery throws errors on cluster nodes
  • Fixed event log category for “DB Engine Seed” discovery
  • Fixed alert message in “Memory-Optimized Data Stale Checkpoint File Pairs Ratio” monitor
  • Fixed issues in cookdown of “User Policy” and “General Always On” discoveries that caused performance degradation in workflows
  • Fixed: “Service Principal Name Configuration Status” monitor throws errors when computer is not domain-joined
  • Fixed “Database Log Backup Status” monitor for SQL Server for Linux
  • Fixed list of required permissions for SQL Server 2012 in “Securables Configuration Status” monitor
  • Fixed: “Database User Policy” discovery failures for AG secondary replica
  • Fixed event log source description of “VLF Count” performance rule for SQL Server on Linux
  • Fixed performance rules for SQL Server 2017 Integration Services

 

SQL Server 2017+ Replication MP Changelog

  • Supported last changes in version-agnostic management pack for SQL Server

 

SQL Server 2017+ Reporting Services MP Changelog

  • Supported last changes in version-agnostic management pack for SQL Server

 

6 Comments
Visitor

Great to see!

A few questions, though:

1) Is there a plan to update the SQL Server Dashboards to work with the new HTML5 web console?

2) Will the Analysis Sevices, Reporting Services, and Replication packs be updated to accommodate the new version agnostic MPs? Or better still, included with the new MPs?

3) Would it be possible to get an update SQLServerMPWorkflowList.pdf?  This is very useful to be able to provide to my DBAs in order to ensure that they are getting exactly what they want monitored.

Microsoft

@mkmaster78 thank you for your questions. 

  1. We're currently working on creating an HTML5 version of SQL Server Dashboards. There's no precise plan yet, the feature will be introduced in one of the upcoming releases.
  2. We don’t have anything to announce here yet.
  3. The download page has been updated. You can now download the workflow list.
Occasional Visitor

I have installed the version MPs 2008,2012,2014,2016. Should I remove the 2014-2016 MP:s when installing this one?

Microsoft

@Jannep when you install the version-agnostic management pack on SCOM where there already are the version-specific MPs for SQL 2008-2016, the new management pack won't discover and monitor SQL 2012-2016 by default. It was made to avoid double monitoring. If you want to monitor SQL 2012-2016 with the new management pack, you can either remove the version-specific management packs before importing the new one or, if you have already imported it, override the DB Engine discovery so it begins to discover SQL 2008-2016. Also, in the latter case, it's up to you when to remove the version-specific MPs - before or after enabling the new MP to discover SQL 2012-2016. 

 

How to enable the monitoring of SQL 2012-2016 is described in the operations guide to this management pack in the section "Turning on the monitoring of SQL Server 2012-2016."

Senior Member

Just wondering why the "Tcp Port" property of the Database Engines is not included in this management pack, whereas it was in the version-specific management packs.  Having this available for inventory/general info is very important to our DBA'a and they are quite upset to see it missing.  Hopefully it can be added back in a future update...?  Thanks.

Microsoft

Thanks for the feedback. This is a popular ask. The plan is to introduce it back in the next update (no timeline to share yet).