You are spot on. While not technically an "issue" or bug.... this was a design change. SQL 2014 does not use the same base classes as all the other SQL MP's do. This means you no longer have a base class you can use for custom workflows which you prefer to be version agnostic. (like SQL DB Engine)
I am running this up the chain to see if I can get an answer for why we did this.... but it was likely very intentional. Microsoft MP's create new rules and monitors for each version of SQL, because capabilities, perf counters, commands, can change between versions. We do the same for all applications including the Base OS. However, I do recognize that customers like a simple base class and write their custom workflows to be version agnostic.... and now this won't work. My recommendation at this point would be to create your own custom class which would discover instances of SQL DB engine, across any version. You have to be careful writing this discovery as you must handle clusters, multi-instance boxes, etc. It would likely be a modified script of our 2005-2012 based discoveries. Then you'd have to re-build all your custom workflows. Or you could simply just write your custom workflows per-version, which is the way Microsoft supplies them. From: [email protected] [mailto:[email protected]] On Behalf Of Gareth Miles Sent: Thursday, May 28, 2015 4:22 AM To: [email protected] Subject: [msmom] SQL 2014 and SQL DB Engine Monitoring Hi I'm looking for some advice. I havn't seen any posts on this, if there have been, please forward to me, thanks. I'm using SCOM 2012 SP1. I have the SQL 2005,2008,2012 and 2014 MP installed. SQL DB Engine covers SQL server 2005 DB Engine, SQL server 2008 DB Engine, SQL server 2012 DB Engine, not SQL server2014 DB Engine. All of my Rules/Monitors that are targeted at DBEngine are targeted at SQL DB Engine, which means they don't run for, SQL server2014 DB Engine. The way I see it I have 2 options. 1. I can create a new class that includes the DBEngine for each version including 2014. This would mean existing rules/monitors targeted at SQL DB Engine would need to be changed. 2. I can create new Rules/Monitors for SQL server2014 DB Engine, this is not a reasonable solution though. What are others doing to get round this issue? Thanks [Signature - Gareth Miles] ________________________________ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Furthermore, the information contained in this message, and any attachments thereto, is for information purposes only and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of the company. ________________________________
