What sql server isolation level should I choose to prevent concurrent reads?

Posted by Brian Bolton on Stack Overflow See other posts from Stack Overflow or by Brian Bolton
Published on 2010-04-09T13:50:47Z Indexed on 2010/04/09 13:53 UTC
Read the original article Hit count: 278

I have the following transaction:

  1. SQL inserts a 1 new record into a table called tbl_document
  2. SQL deletes all records matching a criteria in another table called tbl_attachment
  3. SQL inserts multiple records into the tbl_attachment

Until this transaction finishes, I don't want others users to be aware of the (1) new records in tbl_document, (2) deleted records in tbl_attachment, and (3) modified records in tbl_attachment.

Would Read Committed Isolation be the correct isolation level?

© Stack Overflow or respective owner

Related posts about sql-server-2005

Related posts about transactions