SQLWATCH 2.2
- [New] functionality to raise alerts and send notifications (email, push) or perform remedial actions
- Fully customisable and parameterised alerting engine with configurable templates
- Self-checking mechanism with a number of pre-configured checks to ensure optimum SQL health.
- Template-based reporting functionality to send scheduled reports with a number of preconfigured reports.
- [New] Ability to push collected data to the Azure Log Monitor
- [New] trend tables for very long term storage 2+ years with a reduced storage utilisation
- [New] Table size and row count collector
- [New] Baselines - the ability to display the same metrics offset by 1 day, 1 week or 1 month on the same dashboard.
- [New] Explicit exclusions to be able to exclude certain databases and tables from the collection
- [New] Explicit inclusions for the heavy collectors such as index histogram collection to only collect selected objects rather than everything - exclusion.
- [New] Ability to use Windows Task Scheduler to invoke collectors to make it work on SQL Express Edition and to use SQL Express as a central repository.
- [New] Ability to use the Linked Server instead of SSIS to pull data into the central repository.
...
- [Bugfix] fix handling of timezones.
- [Bugfix] allow indexes with the same name exist in different databases.
- [Bugfix] detect
sp_whoisactive
installed in the SQLWATCH database. - [Bugfix] fix disk size overflow error on large disks.
- [Bugfix] fix formatting of storage units thank you PierreLetter.
- [Bugfix] fix SQL version not being pulled into the central repository
- [Bugfix] fix name of the SSRS database thank you halinegv
...
- Number of other improvements and tweaks
- Aligned wait stat categorisation with the tigertoolbox