anchor.diff:  Implicit a.k.a Ambient Transactions
   -------------------------------------
   
  -It's tedious to pass around connection/transaction pair over and over again. 
  -.NET BCL class [TransactionScope](https://msdn.microsoft.com/en-us/library/system.transactions.transactionscope.aspx) was design to address this issue.
  -Basic idea is that all database connections opened within specific scope are enlisted in that transaction.
  -
  -Example above can be re-written as following:
  +It can become tedious to pass around a connection or transaction pair over and over again. 
  +Fortunately, the .NET BCL class [TransactionScope](https://msdn.microsoft.com/en-us/library/system.transactions.transactionscope.aspx) was designed to address such tediousness. The basic idea is that all database connections opened within specific scope are included in that transaction. Thus, the example above can be re-written as follows:
   *)
   
   open System.Transactions
  
positive.code: 
  Explicit Transactions
  -------------------------------------
  Command types generated by both SqlCommandProvider and SqlProgrammabilityProvider have a constructor that accepts connection instance and optionally transaction. 
  This conforms familiar [ADO.NET conventions](https://msdn.microsoft.com/en-us/library/352y4sff.aspx) for commands constructors. 
  *)
  
  open System
  
negative.code: 
  <div class="well well-small" style="margin:0px 70px 0px 20px;">
  
  This chapter assumes a basic understanding of the "Transactions and Concurrency" topic as it applies to ADO.NET and SQL Server. 
  (If you need to brush up your knowledge use favorite search engine \- there is plenty of information on the subject.)
  
  The following links may be helpful:
  
   - Chapter 9 of [Microsoft SQL Server 2012 T-SQL Fundamentals](http://www.amazon.com/gp/product/0735658145). 
   - [Transactions and Concurrency in ADO.NET](https://msdn.microsoft.com/en-us/library/777e5ebh.aspx). 
  