Category: News

SQLWATCH v2.2 beta 2.2.7275.26487

The latest SQLWATCH 2.2. Beta is now available: https://github.com/marcingminski/sqlwatch/releases/tag/2.2.7275.26487 It can be installed via dbatools using the -PreRelease switch Added Baselines to PowerBI Dashboard so we can see an overlay of performance data from past day, week and month. Added more default Checks Log Growths Errors/sec Logins/sec Page life expectancy Buffer cache hit ratio Memory Grants Pending Memory Grants Outstanding Number of Deadlocks/sec Readahead pages/sec Lock Waits/sec Lock Timeouts/sec Lock Requests/sec Average Wait Time (ms) Page writes/sec Page Lookups Rate Page reads/sec Lazy writes/sec Free list stalls/sec Page Split Rate SQL Re-Compilations Rate SQL Compilations Rate Full Scan Rate Long

SQLWATCH 2.1 is now available

Fixed Cartesian product bug introduced in 2.0 Re-worked PBI dashboard to remove custom data retrieval functions to utilise Direct Queries and benefit from Query Folding. It should now be also possible to deploy dashboard to the PBI Service and schedule it. As part of this work, PBI schema was simplified and GUIDs are no longer required. I have therefore migrated keys from GUIDs to numerical values which saves the storage utilisation. Further schema improvements reducing storage requirements by ~40-60% Started adding views that serve pre-calculated data for reporting which can be fed into any dash boarding solution. To improve reporting

SQLWATCH 2.0 beta 5

A number of fixes in beta 5, mainly addressed extended events collectors that resulted in no data being shown on the dashboard. fixed Better handling of different collations in job deployment mechanism fixed Address INT2 wait_stats overflow on busy systems. On busy systems the correlation sequence is over smallint allocation (32k). fixed Added missing XES collection steps to the performance collector job. Some collectors were not running Beta 4. fixed Better handling of empty wait_info recordset for default system_health session. Collection would fail if there was no recorded waits in the default session. fixed Improved deployment of multi-step jobs. fixed

SQLWATCH 2.0 beta 4

I am happy to announce SQLWATCH 2.0 beta 4 which includes the following changes: New XE Sessions [new] #68 – New Extended event session (SQLWATCH_waits) to capture wait stats over 1 second. By default, this session is disabled. There is no requirement to run it. If you chose not to, SQLWATCH will use the default system_health session to get waits details. The difference is that the default session logs waits over 15 seconds and it takes more time to parse the results due to its size. The SQLWATCH session has been optimised for reading and offloading into table. This session

SQLWATCH Dashboard 2.0 beta 3

After long weeks and sleepless nights with PowerBI, DAX and SQL I am proud to announce the next release of SQLWATCH. Although I have kept database changes to minimal and low risk (only one table added) I have redesigned and rebuilt the PowerBI dashboard from the grounds and thus I am going to keep it in beta whilst I am testing it. There are also few small issues and tidying up I am still dealing with. Multi-Server Dashboard Completely redesigned multi-server dashboard with dark theme. You can now see all of your servers and their issues on one screen. The

Deploy SQLWATCH with dbatools

I am happy to announce that thanks to our fantastic SQL Server Community it is now possible to deploy SQLWATCH using dbatools. If you work with SQL Server and are not familiar with dbatools you should check it out now, it will change your DBA life forever. With dbatools we can now streamline deployments and updates of SQLWATCH across the entire SQL Server estate in a matter of minutes. Installation Install-DbaSqlWatch -SqlInstance SQL-TEST-1,SQL-TEST-2,SQL-TEST-3 -Database SQLWATCH Watch the below example: Update Behind the scenes, the deployment is done using dacpac and operates on the desired state configuration approach which means it will

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.

Development progress w/e 23/09/2018 (Version 1.2)

A first part of the index advisor module – the missing index dashboard is now released and available for download. I have been experimenting with different charts to best show the impact of the missing indexes. Any feedback welcome. Big thanks to ColinDouglas92 for contributing to this release

Development progress w/e 16/09/2018 (Version 1.1)

New PowerBI dashboard to show disk utilisation is now available. Initially, I wanted just one dashboard. I much prefer to have all the information available on different tabs of the same report rather than having to open (and maintain) multiple PowerBI dashboards. However, disk utilisation data is tied to a different snapshot_id (2), is point-in-time, collected at a different interval and kept for a longer time. PowerBI always downloads all data sets when refreshed which would mean that if we only wanted to see last 60 minutes of SQL Performance Activity, PowerBI would also (very kindly) download storage data which would impact the performance of the SQL Server and the PowerBI dashboard. This could be addressed if PowerBI handled composite primary keys without workarounds. It can only use single columns to build relationships between tables which would cause duplicate values in the snapshot_header if we didn’t also make the snapshot_type_id part of the relation.

Development progress w/e 09/09/2018

For the past week, I have been writing SQLWATCH documentation which is now available at https://sqlwatch.io/docs/.  It is still being updated so if you do not find what you are looking for please contact the Team on the #sqlwatch channel on sqlcommunity.slack.com or raise an issue/feature request on GitHub. Last week’s work includes: The new snapshot_type concept has been promoted live, a new primary key for the database is in testing, a new naming standard is being introduced, DACPAC versioning is being introduced and a disk utilisation logger is now in testing.

This site, like most websites, uses cookies. By continuing to use this website, you agree to their use.