InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 20 Jun 2013 05:28:46 GMT20http://www.sqlservercentral.com/Forums/Topic591685-146-1.aspxjeff the prob is even if i m running on 1 stage at a time my IO is slowly increasing and cache hit ratio is below 60 % there where some query which wer using doing table scan that has been sorted on...Mon, 27 Oct 2008 06:04:17 GMTsabyhttp://www.sqlservercentral.com/Forums/Topic591685-146-1.aspxHave you looked in "parameter sniffing" like I suggested above?Mon, 27 Oct 2008 05:56:21 GMTJeff Modenhttp://www.sqlservercentral.com/Forums/Topic591685-146-1.aspxHeh... me too... as previously stated, there's just not enough info to help here.Mon, 27 Oct 2008 05:55:04 GMTJeff Modenhttp://www.sqlservercentral.com/Forums/Topic591685-146-1.aspxwaiting for the reply.Mon, 27 Oct 2008 05:45:27 GMTsabyhttp://www.sqlservercentral.com/Forums/Topic591685-146-1.aspxthe only difference in the stages is stage 1 wil calulate for stage 1 and after the 1st stage gets fully completed it will go to the next stage and soo on .....but i dnt no y disk IO is not increasing so much after 35 stages and cache hit ratio is dam low ...may i know wat can be the reason for cache hit ratioSun, 26 Oct 2008 23:29:55 GMTsabyhttp://www.sqlservercentral.com/Forums/Topic591685-146-1.aspxIt sounds like you're passing each stage as a parameter and that you're looping through each stage. It sounds like each stage may be different enough where you are actually experiencing a phenomenon known as "parameter sniffing" whereby the previous set of parameters setup a particular execution plan that is no good for the current parameter.It's too long to list here... search for "parameter sniff" on the web for more info.Sat, 25 Oct 2008 09:54:10 GMTJeff Modenhttp://www.sqlservercentral.com/Forums/Topic591685-146-1.aspxIt's hard to get you something to do because there isn't enough information here. The low cahce hit ratio makes me wonder if your data is significantly diverse that you can't cache enough. If you watch the execution plans for the states, are they all the same? What is the difference in the stages?Sat, 25 Oct 2008 08:58:25 GMTSteve Jones - SSC Editorhttp://www.sqlservercentral.com/Forums/Topic591685-146-1.aspxhi all m having an issue ...we are having a server contains 28 gb ram ... 20 gb given to sqlserver ,x64 enterprise ,windows 2003database size 5 GBwe are having an application which goes 100 stages ....all the stages are same which runs a proc ...for every 1 stage took 5 mins after 35 stages the time increased and after 70 stages it is taking 35 mins wen i 1st checked the counters total target memory and Target server Memory wer same and then after stage 35 total target memory was less then Target server Memory disk IO is not increasing as it was increasing cpu utilization is normal 14 % buffer cache hit ratio is 99.20 and cache hit ratio is avg 55 % for 35 the stages after 35 it increased to more than 70 %.wen using who2 active it shows cpu 463781 disk IO 406Please provide me the solution i m not getin what exactly the reason is...Sat, 25 Oct 2008 06:26:15 GMTsaby