ColdFusion stored procedure question

I posted this on CF-talk, so sorry for the double-post, but I wasn't getting any response there and this is as much a server question as not. ---------- I have a page with a stored procedure on it.  After the stored proc runs, I have a database call to set some variables.  The variables aren't getting set in the database occasionally.  It also seems that the stored procedure, before the variables are set, times out at occasionally, according to the logs.  If a stored procedure times out, should the rest of the script run?  I don't know if that's the cause of the stored proc is timing out.  Maybe the cf page is timing out from the stored proc timing out. I have no access to the server that is having the problem because it's in production. thanks for any information.  back to googling.

Can you get a test page into production? You might need to find out if its only this stored procedure that is timing out. Can you run a conventional query that does the same thing and test it? ----- Excess quoted text cut - see Original Post for more -----

>Can you get a test page into production? > >You might need to find out if its only this stored procedure that is timing out. > >Can you run a conventional query that does the same thing and test it? I can not get a test page onto production.  I know that it's running half way through the page fine because data is updated in those update sql scripts.  After that, there's a bunch of if/else statement.  The first thing in each of those if/else statements is this stored procedure.  There is information that should be updated after that stored procedure, none of which are being updated.  This led me to the stored procedure as the possible culprit. Still, what is the expected action of the page if the stored procedure times out? I know I can set a timeout to a query, but not to a stored procedure.  If it does time out, what happens to the rest of the cold fusion page?  I'm trying to determine the reason that the rest of the fields aren't being updated. thanks!

It sounds like the code is written to not fail if the procedure does. CF normally just waits for the dB to return something. Your guess about the timeout could be correct and you may need to see what the dB is doing when it should be completing your procedure. I could only be more definite if I had a test setup that imitated your production server and dB People write this 'silent fail' type of code all the time when they think they dont have to own the problem that is causing the failure. (e.g. maybe the dB admin needs to look at backups to see if they hog resources just when your proc needs them) ----- Excess quoted text cut - see Original Post for more -----

also, the problem is not regular, just sporadic.  The problem occours maybe 20 times out of 10,000. daniel