Monday, May 19, 2014

As a SQL Server DBA, Why Do I Need Performance Advisor for Windows?



Performance Advisor for Windows for the SQL Server DBA


SQL Sentry Performance Advisor (PA) for Windows is one of our newer product offerings, and I think one that could use a little bit of use-case clarification.  I am often asked questions like this: “Why would I need Performance Advisor for Windows when Performance Advisor for SQL Server already shows me Windows metrics?”
There are several possible answers to this question.
  • You really don’t need it, PA for SQL Server has you covered.
  • You need visibility into other Windows Servers that aren’t monitored by Performance Advisor for SQL Server.
  • You need additional visibility into other things running on one or more of your monitored SQL Servers.
Before we talk about each of the three answers above, let’s go over what Performance Advisor for Windows does:
  • Adds the Processes Tab.
  • Adds process group highlighting to the PA Dashboard.
  • Allows monitoring of any Windows machine with the Windows portion of the PA Dashboard and the Processes Tab.

You really don’t need it, PA for SQL Server has you covered.

The bright green for "other" here really doesn't have much of a story to tell.

This is the easy one.  In the case of a standalone SQL Server instance with few to no other running services aside from the OS, you probably don’t need PA for Windows, as there 
won’t be a need to see details on the “other” Network, CPU, and Memory metrics very often.  In this case, you are probably going to be just fine with PA for SQL Server by itself.

You need visibility into other Windows Servers that aren’t monitored by Performance Advisor for SQL Server.

PA for Windows gives you live and historical performance monitoring for any Windows Server

There are lots of use cases for this.  If you are responsible for monitoring other servers in the environment that aren’t running SQL Server, PA for Windows offers a great solution.  Often, for users of PA for SQL Server these are servers that interact with your SQL Servers: VM Hosts, Sharepoint Farm Servers, App Servers, Servers used in ETL processes, and so on.  This is helpful because a SQL Sentry user can create consolidated views of related servers, and easily drill into problems.

You need additional visibility into other things running on one or more of your monitored SQL Servers.

That's better!  Now we have visibility into other process groups on the dashboard.

The processes tab gives even more details.
If you find yourself wondering what makes up the “Other” category that you see on the PA for SQL Server dashboard, those details can be collected and shown by PA for Windows.  Well-known processes will have predefined color highlights, and highlights for other processes not automatically recognized by SQL Sentry can be created with a quick update to the SQL Sentry Database.  Detailed utilization metrics are also available on the Processes tab which is also available in the Jump To menu for drilldown.  This is gives the user a way to see what is happening with processes like Reporting Services, Integration Services, Internet Information Services, third-party backup tools, and other things that might be running alongside the SQL Server process.

I hope this helps clear up the use cases, and what PA for Windows adds to servers already monitored by PA for SQL Server.  Please comment or contact us with any questions.

1 comment:

  1. Kevin, I always appreciate and admire a sales pitch that's willing to state "Maybe you don't need it."

    That's a refreshing attitude, and likely to drive sales because your potential customers can more confidently determine their actual needs and your products' ability to service them.

    ReplyDelete