title: What transaction isolation level should I use
body: <p>I am working on a custom application that allows users to insert / update / delete / retrieve data from a database.</p>
  
  <p>Stored procedures I use affects a few tables so I use a transaction and I want to be able to lock these tables to prevent unintended things from happening when multiple users are inserting , deleting, updating, or retrieving (CRUD) data.</p>
  
  <p>My question is what would be the best isolation level to use here, I have read the MSDN on isolation levels and tried to make sense of it as well as searching around, If someone who has been here done that could comment quickly that would be greatly appreciated.</p>