Contact Us

Dear SMT users,

After about two months we have another update for Server Monitoring Tool available for you. The version is now 00.5.70 and the updates are ongoing. Some of our clients have already been informed in a bit more detail about the changes by one of my colleagues on a regular meeting, the rest will get the introduction on the upcoming session.  

Here is a brief summary of all the changes included.

  • The way how we collect data about the query performance statistics related statements and query plans has been changed.
  • A set of new reports to help performance tuning has been added;
    • Query search - based on the part of the code you can search and view collected performance statistics.
    • Performance compare – report to compare query statistics in two different intervals.
    • New report to better analyse the BLOCK chains and reveal HEADBLOCKER.
  • We are now collecting and reporting performance statistics related to triggers.
  • New report to track Configuration History.
  • New report to analyse Volatile Jobs.
  • We changed a bit the menu structure to group related reports and make it more intuitive.
  • Already existing alert for tempdb size was extended with a new check.
  • The storage reports is now able to show data from DWH.
  • Miscellaneous minor bugfixes, enhancements and adjustments.

For the new reports we tried to add enough information to make it easier for you to use those.

Please contact us in case you have any questions or suggestions, we would be happy to discuss them.

We will start scoping a new release soon. I am sure that a another set of helpful stuff and enhancements will be delivered for you to us in SMT.

Kind Regards,

Jiri Dolezalek

 

More tips and tricks

SMT 1.13 Introduces more QOL features and Replication Monitor
by Michal Tinthofer on 12/09/2025

As we finalize the upcoming release, we want to share with you what is coming.

Read more
The Symmetry of Performance: Solving CPU Wait Spikes by Disabling Soft-NUMA
by Michal Kovaľ on 17/02/2026

In high-performance SQL Server environments, how you "slice" your CPU resources is just as important as how many cores you have. We recently tackled a case where a customer was plagued by high SOS_SCHEDULER_YIELD and CXPACKET waits.

Read more
Collation conflict
by Michal Tinthofer on 07/03/2012

I think there is more simple and harmless way. First we need to understand the process of tempdb collation setting.

Read more