We\'ve been seeing this problem for a while now and I\'m really trying to wrap my head around what\'s causing it.
A couple of times a day we\'ll see periods where we
I solved this problem by recreating the stored procedure!
Just a simple DROP
and then CREATE
stopped the timeouts in my case!
I had suffered with this problem for a week; a classic ASP said "SQL timeout" when I could run the same query direct on the database in less than a second. (I did not see the "does not exist" message though.) The ASP had been working fine for a whole month.
A genius friend of mine said, "Going through ASP uses a 'cached' execution plan, which is not very efficient. Try dropping and recreating. This does suggest your stored procedure could do with re-writing to make it more efficient, as it could happen again."
Since the proc was running fine when tested with SQL Management Studio, I assume that does not used the cached plan, but ASP does.