Collation conflict
by Michal Tinthofer on 07/03/2012I think there is more simple and harmless way. First we need to understand the process of tempdb collation setting.
Read moreWe just released set of changes, enhancements and a few fixes marked as SMT version 1.2.
What has been done in this release?
While we are releasing this version, we are already planning and working on new changes and modules so you can look forward for a next update. Everybody on SMT 1.1 will get the new version in next 24hours through the automated upgrade process.
Please contact our team if you have any questions, which we will be more than happy to answer.
For SMT development team Jiri Dolezalek.
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.
I think there is more simple and harmless way. First we need to understand the process of tempdb collation setting.
Read moreRecently, we found an interesting pattern during exploring one of our SMT graphs while doing a health check of a SQL server. The following graph shows us the Load Factor attribute. The value came from system table sys.dm_os_schedulers, which the SMT tool
Read moreImagine opening SQL Server Management Studio (SSMS) on a Monday morning and finding… nothing.
Read more