November 12, 2003 at 9:48 pm
Hi,
i am executing stored procedure from VB application. when i run first time it is giving timedout message. when stop apps and re-run the application its working fine. i am thinking this is happening because first time data is not there in the memory. second time data is in memory so its running fine.
is there any thing is need to do by dba or me.
Thanks
ravi
November 13, 2003 at 1:26 am
The first thing to check in this case is the VB config.
Check if you have the same issue when you execute your proc within QA.
Also check the response (and execution time) within QA.
If that one seems to be OK, then you have to check your VB connection parameters.
Never the less I think that this problem not really SQLServer related.
I'm often freeing up the memory cache when I'm doing benchmarking and I'm never getting to timeout.
The only times I was experiencing timeout problems when I was using a modem dial up connection out of EM.
Bye
Gabor
Bye
Gabor
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply