Can transaction failure event handler be implemented on a Web-based app?

Can transaction failure event handler be implemented on a Web-based application in which either records will be inserted or updated in about 10 tables?
To handle transactions you have to use ADO.NET features. It's not a matter of Web-based or Windows-based applications. ADO.NET provides a BeginTransaction() method for all objects implementing IDbConnection (such as OleDbConnection and SqlConnection). This method returns an IDbTransaction object you can use to commit or rollback an entire operation. The typical usage pattern is:

Download this free guide

Download: The Developer's Guide to IoT

The IoT world may be exciting, but there are serious technical challenges that need to be addressed, especially by developers. In this handbook, learn how to meet the security, analytics, and testing requirements for IoT applications.

Start Download

• Corporate E-mail Address:

  You forgot to provide an Email Address.

  This email address doesn’t appear to be valid.

  This email address is already registered. Please login.

  You have exceeded the maximum character limit.

  Please provide a Corporate E-mail Address.

By submitting my Email address I confirm that I have read and accepted the Terms of Use and Declaration of Consent.

By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.

You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

IDbConnection cn = new SqlConnection("your connection string");
IDbTransaction trans = cn.BeginTransaction();
try
{
	//try to update/insert everything using cn as the connection
	//Use cn.CreateCommand() to get IDbCommand to execute queries.
	trans.Commit();
}
catch 
{
	//cancel
	trans.Rollback();
}
finally
{
	cn.Close();
}

Using the ADO.NET interfaces instead of the SqlClient classes directly, makes it far easier to port this code later to another DB engine. In the case shown above, only the first line that creates the new SqlConnection would need to be changed. Better yet, you could use an abstract factory so you have a single point of change in the future.