|
-
Jun 30th, 1999, 06:43 PM
#1
Thread Starter
New Member
I am trying to execute a stored procedure on an MSSQL Server. I
have set my CommandTimeout value equal to zero but it the stored
procedure only handles a few records and then the
ExecuteComplete event occurs.
Does anyone know why my stored procedure will not fully complete
it's task before ending? Also, does anyone have any suggestions
on how I can temporarily hold my program while the stored
procedure is running? I do not want it to continue until the
stored procedure is complete or I will have problems.
Thanks
-
Jan 25th, 2002, 10:48 AM
#2
New Member
did you ever get a reply on this
did you ever get a reply on this
-
Jan 25th, 2002, 11:15 AM
#3
Fanatic Member
What does your procedure do? Is it a Select, Insert, Update...?
-
Jan 28th, 2002, 09:56 AM
#4
New Member
What does your procedure do? Is it a Select, Insert, Update...?
What does your procedure do? Is it a Select, Insert, Update...?
Yes, Yes, and Yes.
We have a procedure that responsible to call a whole host of other procs that perform various and sundry functions of select insert and update. The main proc, with moderately sized data could take 2-3 min to process.
ps If:
It's 1440 on Monday, and everything is just fine, fine, fine.
Then:
You aint from around here then are you? Its 0900 on Monday here.
Jon
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|