Re: ADO.NET Timout
- From: "Mary Chipman [MSFT]" <mchip@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 16 Jun 2006 14:05:18 -0400
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
- From: Lit
- Re: ADO.NET Timout
- References:
- ADO.NET Timout
- From: Lit
- ADO.NET Timout
- Prev by Date: Re: Can't get DataView to sort correctly.
- Next by Date: Best practices for using Connections in connected environment?
- Previous by thread: ADO.NET Timout
- Next by thread: Re: ADO.NET Timout
- Index(es):
Relevant Pages
|
Loading