Replies: 1 comment
-
The Community Tools feature allows you to run community procs on demand from the DBA Dash GUI. It can't be used in combination with alerts. It is possible to use a custom collection to run sp_BlitzWho on a schedule. A wrapper proc could be used to supply the parameters to sp_BlitzWho and only trigger it under certain conditions like CPU usage. A built-in SQL Server alert could also be considered (which can trigger a job). Or just an agent job that runs periodically with a CPU condition check. The Running Queries tab in DBA Dash is very similar to sp_BlitzWho, and it will provide the data you need with less overhead for regular data collection, most of the time. There are reasons why you might prefer sp_BlitzWho - like the live query plan capture. While this is useful, there will be significant additional storage costs to capturing this data regularly compared to Running Queries. In most cases, it's not required - DBA Dash can capture the query plan without the runtime stats. If slow query capture is enabled, this also gives you the parameters so you can run the query later to capture the actual plan (the compiled parameters are also in the captured plan if needed). The alert feature can be used to send email alerts if the CPU goes over a certain threshold or various other performance conditions. It can also send other types of alert notifications - Slack, Google Chat, Pager Duty etc. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
It will be possible to run a Community Tools in case of a problem? Like High CPU usage? Alert can do that? Send an Email and run a script. Or i can create a report for SP_BlitzWho triggered by an event?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions