The other day I was asking why I might be getting hash and sort warnings (in profiler) when the server had 20gb free, and the best answer was that maybe the stats were out of date. I have not had time to investigate that one further.
Instead I've been on some systems with much tighter RAM, so there is some excuse for these warnings, yet now that I look closely they are for queries that even with the warnings, execute in 100 to 200ms, with just 3500 reads.
The queries are selects that join a temp table with 300 rows to a big, fat permanent table that does have an index on the joined column.
For good luck I updated the stats on the big, fat table - and this had no noticeable effect.
So I guess the question is, just how sensitive are these hash and sort warnings?
Hash warning is 0 - recursion.
Sort warnings are 1 - single on one query and 2 - multiple on the second query.
Thanks.
Josh
(fwiw this is the previous thread)
