Re: ADO.NET Transaction
- From: "William Vaughn" <billvaNoSPAM@xxxxxxxxx>
- Date: Thu, 9 Aug 2007 10:29:22 -0700
Ah, I don't have the time and you don't have the patience to wait until I do... ;)
Nothing is ever "always bad" just as nothing is "always good". XML has its place. It's just been misused by too many that should know better.
Client transactions put too much schema-dependent, business-rule-dependant code on the client. I think more logic should be run from a common platform.
I discuss these issues in most of my books--even the latest. See Chapter 1 that discusses architectures...
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------
"Lit" <sql_agentman@xxxxxxxxxxx> wrote in message news:eDMn4Fq2HHA.728@xxxxxxxxxxxxxxxxxxxxxxx
William,
What about when you have to process and send lists?
I know I can send XML to SQL
Is it always a bad reason to do client transactions?
Can you tell me more about your "bad" experience of client transactions I am all ears.
I would love to hear some good or bad stories so I can decide what to do.
Thank you,
Lit
"William Vaughn" <billvaNoSPAM@xxxxxxxxx> wrote in message news:O%23fHn8h2HHA.5164@xxxxxxxxxxxxxxxxxxxxxxxIf it were me I would probably call a stored procedure that started the transaction ran all of the SPs, handled the exceptions, channeled the logic and returned success or failure via RETURN... but that's just me. I'm not a fan of client-side transactions...
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------
"Lit" <sql_agentman@xxxxxxxxxxx> wrote in message news:e0$W7bg2HHA.6072@xxxxxxxxxxxxxxxxxxxxxxxHello,
using ADO.NET 2.0, VS.NET 2005, SQL2005
I need to execute several Stored Procedures under one transaction. Can I use just one transaction or have to use multiple ( then commit or rollback all )
How does it work with ADO.NET
Ado.Tran
SP1 Called
loop
SP2 Called
SP3 Called
loop
SP4 Called
loop
Sp5 Called
Etc... etc...
if any error
rollback transaction ( or all transactions )
else
committe Transaction ( or all Transactions )
Thanks for any help or other Ideas
Lit
.
- Follow-Ups:
- Re: ADO.NET Transaction
- From: Lit
- Re: ADO.NET Transaction
- References:
- ADO.NET Transaction
- From: Lit
- Re: ADO.NET Transaction
- From: William Vaughn
- Re: ADO.NET Transaction
- From: Lit
- ADO.NET Transaction
- Prev by Date: Unit Test returns dataprovider while running the app itself is not able to find the dataprovider
- Next by Date: Re: using typed dataset with data relations?
- Previous by thread: Re: ADO.NET Transaction
- Next by thread: Re: ADO.NET Transaction
- Index(es):
Relevant Pages
|
Loading
