Using Transactions really comes down to scenarios where you can't afford to have one table update without another one updating. If that is the case then you need to use transactions. You will need to handle the transaction in Stored Procedures or in ADO.NET.

Here are some articles:

http://aspalliance.com/hrmalik/articles/transactions.aspx

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/disttranvbnet.asp

http://www.csharphelp.com/archives/archive224.html

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/bdadotnettransact1.asp


>All,
>
>I am looking to add transaction processing to my application. I do not see much about this in articles and was wondering if it is really necessary or is it already handled in the database?
>
>Is it a function of complexity? If I have a process which involves many table updates or in an application such as banking where the transaction needs to be complete before money is released I can see the need, but is transaction processing always necessary?
>
>TIA
>
>Rex