SQLWATCH needs your help #SQLFamily
Hey SQLWatchers, First of all, thank you for the growing [...]
Cards in Microsoft Teams Notifications with action templates
In the previous post, I have explained how to configure [...]
How to send notifications to Slack
Some time ago we discussed how to send notifications to [...]
Deploy SQLWATCH with dbatools
I am happy to announce that thanks to our fantastic [...]
How to send notification to Microsoft Teams
I have been meaning to write how to integrate SQLWATCH [...]
Version 4.1 is now available
Contributors @marcingminski and @tarmstrong24 Features Change to parse job name and replace [...]
We’re moving to queues
Some time ago I asked on GitHub whether we should [...]
What’s new in version 3
Version 3 of SQLWATCH brings several, long-awaited features that should [...]
SQLWATCH 2.5 is now available
Fixed an issue where table utilisation was not being collected [...]
Report parameters, time slice and intervals
When retrieving performance data from SQLWATCH database we have to keep in mind the fact that this is a decentralised architecture meaning, we are connecting to possible a production instance and there could be gigabytes of performance data in the SQLWATCH database. For obvious reasons we do not want to pull all the available data into PowerBI as this could impact the service. In this post we are explaining the design behind time parameters.