Re: ADO.NET Timout
- From: "William \(Bill\) Vaughn" <billvaRemoveThis@xxxxxxxxxx>
- Date: Tue, 20 Jun 2006 11:55:17 -0700
Sure it will (timeout). You need to set the Command.Timeout property to the
number of seconds required to complete the operation. 0 :: wait
indefinitely. I don't recommend this approach as your execution thread will
hang indefinitely.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Lit" <sql_agentman@xxxxxxxxxxx> wrote in message
news:Oh9mTPJlGHA.3528@xxxxxxxxxxxxxxxxxxxxxxx
William,
So the 30 sec Connection Timeout will have no effect when a SP called
asynchronously?
Do I still have to give it a higher time value?
What I am trying to do is call a SP and let it execute no matter how long
it takes it.
Being asynchronous does not mean it is not going to timeout?
Thanks
Lit
"William (Bill) Vaughn" <billvaRemoveThis@xxxxxxxxxx> wrote in message
news:O7kzv$IlGHA.4024@xxxxxxxxxxxxxxxxxxxxxxx
A SP can be called asynchronously from ADO.NET (2.0) by using the
BeginExecute method of the Command object. ADO classic supports async ops
as well. I'll be discussing this in my session on Async operations at
VSLive this week (Thursday 11:30) in Vegas.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no
rights.
__________________________________
"Lit" <sql_agentman@xxxxxxxxxxx> wrote in message
news:exSXh3IlGHA.4872@xxxxxxxxxxxxxxxxxxxxxxx
Mary,
How can I call a stored procedure to do its thing asynchronously.
What is the best way of doing this?
Thank You,
Lit
"Mary Chipman [MSFT]" <mchip@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:mfs592l5gnd5lhm1pr28o9mt6q0d5bq1e0@xxxxxxxxxx
If the connection is terminated, then any active transactions that are
occuring inside the stored procedure that have not yet been committed
will be rolled back. Any committed transactions will be preserved. If
you want all work items inside of the stored procedure to be handled
as a single unit of work, you can implement an explicit transaction.
For more information, see "Explicit Transactions" in SQL Server Books
Online.
--Mary
On Wed, 14 Jun 2006 11:53:31 -0700, "Lit" <sql_agentman@xxxxxxxxxxx>
wrote:
Hello,
The default ADO.NET Timeout is 30 seconds.
If I execute a Stored procedure that takes lets say 120 seconds then
what
happens.
ADO.NET Times and throws an exception
But what about SQL Server Does SQL Server keep on Executing the Stored
procedure?
Thanks
Lit
.
- Follow-Ups:
- Re: ADO.NET Timout
- From: Lit
- Re: ADO.NET Timout
- References:
- ADO.NET Timout
- From: Lit
- Re: ADO.NET Timout
- From: Mary Chipman [MSFT]
- Re: ADO.NET Timout
- From: Lit
- Re: ADO.NET Timout
- From: William \(Bill\) Vaughn
- Re: ADO.NET Timout
- From: Lit
- ADO.NET Timout
- Prev by Date: Re: ADO.NET Timout
- Next by Date: Re: ADO.NET Timout
- Previous by thread: Re: ADO.NET Timout
- Next by thread: Re: ADO.NET Timout
- Index(es):
Relevant Pages
|
|