April 24, 2009 at 2:45 am
Hello,
One customer reported client software freezes on every workstation.
They have a dual database server synchronized by Legato. When the freeze occured, they switched to the other database instance.
In the available trace file, before the failover, I see a lot of event "Hash Warning" followed by "Missing Column Statistics" (one every 5 minutes). After the failover, back to normal.
Could those hash warnings cause such an heavy performance breakdown ?
What can I do to fix those warnings ?
Thanks
Patrick Duflot
April 26, 2009 at 7:19 pm
According to MSDN online yeap it can. This can happen because the server doesn't have enough memory, statistics are old or don't exist.
Have a read at http://technet.microsoft.com/en-us/library/ms190736(SQL.90).aspx.
Check how is the server sitting with memory pressure?
Thanks.
Mohit.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
August 13, 2009 at 7:32 am
Good Day,
when will the number of pages/ sec be too excessive for Windows 2008 ?
August 13, 2009 at 7:39 am
Good Day.
I have auto create statistics activated on the database and there is a daily schedule to update the database statistics, but still the default trace displays "Hash Warning" messages . Should we rather consider to activate "auto update statistics" . Will this not cause the creation of unnecessary statistics that can impact the system again ?
August 13, 2009 at 1:20 pm
Better turn it ON unless you see performance degradation due to update stats running on server during peak hours.
http://blogs.msdn.com/ianjo/archive/2005/11/10/491549.aspx
MJ
August 14, 2009 at 2:14 am
Hi Patrick
Can u identify the query that's causing this. Your query is using hashing and this is generally bad for performance. You will want to re-write this query in a better way. Once you are able to do this chances are that missing column statistics will be taken care of. Better concentrate on Hashing issue rather than column statistics.
"Keep Trying"
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply