Many people ask - do I need transactions? Why do I need them?
When to use them?  The answer is simple: use them all the time,
unless you have a very good reason not to (for instance, don't
use atomic transactions for "long running activities" between
businesses). The default should always be yes. You are in doubt?
- use transactions.  Why are transactions beneficial? They help
you deal with crashes, failures, data consistency, error
handling, they help you write simpler code etc. And the list of
benefits will continue to grow with time.  Don't think in terms
of transactions only when you talk to two or more databases.
Starting with technologies like LTM, transactions are made
available to be used for any multi-action operation. "X = A+B; Y
= C*D;" can be transactional or atomic, as some prefer to name
it, and can be seen as a single unit of work.  That is also why
support for transactions is available almost everywhere. In
database systems, in COM+, in ASP.NET, in .Net Framework with
System.Transactions and E