Version 2.1.0 of the PSBlitz SQL Server diagnostics collection and output tool brings bug fixes, quality of life enhancements, and added diagnostics data.
Additional diagnostics data
The following sheets have been added:
- Instance Info – contains an overview of the instance (version, edition, uptime) and its resources
- sp_BlitzWho Aggregate – this makes it easier to interpret active query data on busy instances
- TempDB – contains TempDB space usage data per object type (internal, user, and version store), top 30 temp tables based on reserved space, top 30 sessions based on total TempDB allocation.
Quality of life
- Improved the handling of deadlock graph and execution plan data, leading to generating .rdl and .sqlplan files that contain correctly formatted XML. This makes the resulting files easier to read in XML format with text editors like Notepad++.
- The application name (PSBlitz followed by the version number) is now part of the connection string, making it easier for DBAs and/or monitoring solutions to identify sessions originating from PSBlitz.
- An informational warning will be displayed at the start of PSBlitz’s execution if the instance has less then 7 days of uptime. This is to let users know that some of the diagnostics data might not accurately reflect what has been going on on the instance.
- Changed the file naming convention for for execution plans from sp_BlitzWho to avoid potential file overwrites in rare cases.
The new file naming scheme is
RunningNow_[SPID]_[start_time]_[query_plan_hash].sqlplan, if no query plan hash is returned by sp_BlitzWho, then 0x00 will be used.
- The output workbook now has a different name while PSBlitz is running. This is done in order to avoid potential conflicts when a workbook from a previous run on the same instance is being viewed in Excel.
As usual, the latest version can be found in the Releases section of the PSBlitz GitHub repository.
Leave a Reply