From: "sysadmin.rock[SINESTO]"@gmail.com   
      
   On 05-05-2011 18:56, Erland Sommarskog wrote:   
   > Wishmaster ("sysadmin.rock[SINESTO]"@gmail.com) writes:   
   >> I got this situation, I got a stored procedure that for some reason   
   >> after using it for some period of time (maybe a day or two)  stops   
   >> sending results, but  if I change the position of the condition (where)   
   >> on the first line then begins to work ok.  This solution works a day or   
   >> two but the issue arise again and I must change the line to it's   
   >> original version, completing this weird cycle.  have you ever seen this   
   >> kind of behavior before?   
   >> The first commented line is what i need to change time to time...   
   >   
   > What more exactly do you mean with stop sending results? Does it not   
   > produce a result set at all? Does it only produce an empty result set?   
   > Is there an error message?   
   >   
   > What happens if you run the procedure from Management Studio? If you run   
   > the procedure from Mgmt Studio, after first having executed SET ARITHABORT   
   > OFF?   
   >   
   > Anyway, I would suggest that you add this at the end of the query:   
   >   
   >    OPTION (RECOMPILE)   
   >   
   > Since I assume that this is somehow related to the query plan, I expect that   
   > this should resolve the issue. I would also expect it to improve the overall   
   > performance.   
   >   
   Erland,   
      
   what i'm trying to say is there not any result set on my website and no   
   error message as well. But if i run the stored procedure from Mgnt   
   Studio takes arround  3 minutes to produce a result set.   
   I'm going to check your suggestions.   
   Thank you!   
      
   Diego.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)