Does anyone have suggestions, other than using "set xact_abort on," on how
to handle rolling back a transaction after it's timed out while using
connection pooling?Richard wrote:
> Does anyone have suggestions, other than using "set xact_abort on,"
> on how to handle rolling back a transaction after it's timed out
> while using connection pooling?
Why can't the business layer executing the SQL issue a rollback if a
timeout error is returned from the call?
David Gugick
Quest Software
www.imceda.com
www.quest.com|||That's the only way to handle it I guess. Thanks!
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:%23c0ci9fkFHA.2156@.TK2MSFTNGP14.phx.gbl...
> Richard wrote:
> Why can't the business layer executing the SQL issue a rollback if a
> timeout error is returned from the call?
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
Thursday, March 22, 2012
Connection pooling and timeouts
Labels:
back,
connection,
database,
handle,
microsoft,
mysql,
oracle,
pooling,
rolling,
server,
sql,
timed,
timeouts,
transaction,
xact_abort
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment