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 hope you're doing well and we would like to announce next SMT changes,
We are about 75% done with a roll out of the recently released version SMT 1.0 to our clients but in the meantime, we have also worked on the new features and enhancements.
The new release SMT 1.1 just passed final testing on our stage environment and will be made available in upcoming days to all instances with preceding SMT version (1.0).
The changes in this release consists of the following;
This will be the first release that will be done automatically through SMT-CORE by the daily overnight process. It works in a pull mode, so nothing is pushed to instances, but the instance will get the changes with next regular synchronisation. This has been something that we have been working on for some time and is finally ready to be used.
Do not hesitate to contact us in case you have any questions, also any feedback on the changes is appreciated.
For the SMT team,
Jiri Dolezalek & 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.
I think there is more simple and harmless way. First we need to understand the process of tempdb collation setting.
Read moreYou might have been wondering what all those ANSI settings are and how they can affect you work.
Read moreSMT Waits reports – handy overview of what is going on at the server
Read more