Caruncles (11/20/2012)
Would timing-out errors be a symptom of improper TempDB settings? Especially, during peak times. We are in our busy season right now there is a lot of data entry and updating going on.
It could, in extreme conditions. I have seen it happen during peak times where the log file was already very large, it was still set at default to grow at 10% and an autogrow was invoked causing the log file to need to grow by many gigabytes. Log files must be zero-initialized and on an already busy I/O subsystem a large autogrow operation can be quite disruptive. What were the results from the query in the article on your system?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato