Another developer (lets call her "J") at the office brought this point up to me today. Its not much fun executing (insert, update, delete) statements over and over. specially if one of the statements error. Then I have to go back through each statement and try some form of roll back procedure. J found an article from 4 guys from rolla, on how to use ADO.Net to rollback all your statements. Take a look 

How do you handle commits and rollbacks? All in stored procedures, or ADO.Net?