Modern DBAs know that you measure latency, not queue lengths.Īnd don’t even get me started on the colored lines – I’m red-green colorblind. Metrics – average disk queue length. Awesome – leading with the single least useful disk counter. Zero? ZERO? Come on, now you’re just making stuff up. Again, what does this even mean? What action do you expect a DBA to take based on this headline number? The numbers at the top of the product should be the most important ones, and clearly they’ve had the least amount of thought.
#Apex sql monitor software#
I’m guessing the SQL Server has less than 1TB of RAM (as most do) but the software isn’t smart enough to change the unit of measure to GB in that case, or display decimal points. What the hell does that mean? The server has no memory? That doesn’t even make sense. That’s not a server problem – it’s a monitoring tool problem, expecting humans to deal with that. I can’t expect a DBA to realistically prioritize 128,524 alerts. I get it, it’s probably a demo environment, but that tells me the software is going to spam the bejeezus out of me with alerts that don’t actually matter. I can forgive calling it “SQL server” in a small part of documentation, but on the app’s home page, in the very first screen shot? From a company that focuses on SQL Server? That’s…disappointing.ġ28,524 unchecked alerts. The more things I looked at, the more horrified I got. I clicked on it immediately and looked at the first screen shot in their announcement blog post: ApexSQL Monitor – click to enlarge So when I got an email from ApexSQL announcing their new SQL Server monitoring product, I was excited.
I get really excited when there’s a new one because I think there’s still a lot of space for innovation in this market. Let’s get one thing straight from the start: I love monitoring products.