Today we introduce to you another patch which was focused on several “quality of life “improvements. Most notable was integration of execution plans and statements from waiting tasks report into standardized dimensions we already used in query reports. Now you will always be presented with Query detail or Plan Detail report when you click on text or query plan column in SMT reports. It will dramatically decrease the size of monitoring database.
Another nice feature is paging ability for big tables. Since amount of reported data will grow over time, we introduced this functionality to keep our tool fast as possible even when reporting thousands of rows into table.

 

Here is the full list:

  • Fixed Bug where mail component update all alerts mailed column instead of respective one which is currently notifying.
  • Fix for waiting tasks report, now it will use centralised reports for command texts and execution plans. This will greatly decrease the size of this check in monitored database. Also we splitted report Waiting tasks into two with detail informations about session.
  • In waiting tasks detailed report we also introduced table paging to allow covenient browse through big tables.
  • Fixed an issue where too deep execution plan cannot be collected due to XML type limitations in SQL Server.
  • Fix updated query collection for Phy Reads. Now its count based on real collected data for this dimension.
  • Fix for Memory pool stats not showing all graphs correctly.
  • Fix for Query performance reports showing statement text in execution plans as ** Encrypted Text **.
  • Fixed a bug where index collectors hanged over tempoerary objects for analysis.
  • Fixed bug where index recommendation check didn't finished because duplicate statistics has been reported from the server.
  • Fixed rare bug on some systems where checkpoint pages/sec graf not reported any data.

 

We hope you will continue to enjoy our tool!

With regards, 

Michal Tinthofer.

More tips and tricks

How to check multiple backups stored in one file
by Michal Tinthofer on 26/06/2012

Backup device is a standard backup file. But this file is registered in management studio and often used to store more than one backups from database. There are also some pros and cons in usage compared to standard backups stored in folders and made by ma

Read more
Is model db important?
by Michal Tinthofer on 15/02/2012

Few days ago I have been asked for help in process of installation a SCOM. Admins wasn’t been able to install some parts of this system because installation wizards reports some unexpected errors. When I arrived to the SQL instance I found something inte

Read more
Xmas release 1.5.0
by Jiri Dolezalek on 14/12/2021

SMT Christmas release is ready

Read more