I like to think of SCOM as a great hospital, designed to bring together the best facilities and professionals to deliver the highest level of healthcare to its patients. Just like a hospital, SCOM provides a framework, infrastructure and delivery of the basic healthcare services you would expect. And, just like a hospital, SCOM can’t possibly cover all of the specialities to span the full spectrum of issues that could crop up.
SCOM can be customised to a specific domain, but in the heat of an emergency event, you need to rely on the best in class dedicated resources that can deliver the fastest possible diagnostics and the most reliable root cause analysis. Should trouble with a database occur—and odds are about 100% that it will happen over time—DBAs just aren’t getting what they need to effectively troubleshoot and diagnose performance issues. Think of it this way: your primary care physician can spot a problem, but you’ll likely need a specialist to resolve it and prevent it in the future.
To get the right specialized care for your SQL Server health, it’s important to first understand the areas where SCOM doesn’t fully address your database needs:
With SCOM alone, DBAs would potentially need to write complex scripts to create a picture of server health, leaving them short of all the information necessary to troubleshoot issues. Having complementary solutions that assist in the diagnosis and solutions of problems drastically enhances SCOM’s capabilities. The end result is a great partnership to optimize the health of your SQL Server environment and deliver the great performance that your end users have come to expect.
Want more information on how to maximize your SCOM investment? Read this white paper, “Go Beyond Basic Up/Down Monitoring.” You’ll get expert guidance to extend SCOM’s capabilities with predictive performance diagnostics and best practices for monitoring and troubleshooting your SQL Server environment.