Tool to measure Index Selectivity
by Michal Tinthofer on 05/06/2012Sometimes when you plan to change your index design is good to know the columns of your tables. But not just a data type and max size.
Read moreToday 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.
We hope you will continue to enjoy our tool!
With regards,
Michal Tinthofer.
Michal Tinthofer is the face of the Woodler company which (as he does), is fully committed to complete support of Microsoft SQL Server products to its customers. He often acts as a database architect, performance tuner, administrator, SQL Server monitoring developer (Woodler SMT) and, last but not least, a trainer of people who are developing their skills in this area. His current "Quest" is to help admins and developers to quickly and accurately identify issues related to their work and SQL Server runtime.
Sometimes when you plan to change your index design is good to know the columns of your tables. But not just a data type and max size.
Read moreSometimes is nice to have a tool/report which could allow you to see how much your backup storage is degraded over time. Especially by fragmentation and auto growth/shrink operations.
Read moreI think there is more simple and harmless way. First we need to understand the process of tempdb collation setting.
Read more