isolation level - SQL Server IsolationLevel.ReadUncomitted dangers -



isolation level - SQL Server IsolationLevel.ReadUncomitted dangers -

i'm doing next in readuncommitted transaction on mulitple thread, in old system:

each thread unique set of info work on. there never duplicates across these threads. the threads gather info bunch of tables (only reads) unique info set. based on gathered info each thread create n number of new entities, emails, in memory later writing. then each email entity threads have check if email entity exists in table, avoid duplicates. involves comparing x number of columns. afterwards threads write email entities not exist, knowing clean inserts threads , application ones can write these type of email entities , threads work on unique info sets. then threads commit.

now know not pretty design, it's big task refactor entire system. reason threading purely gain improve performance.

my question is:

are there dangers in using readuncommitted isolationlevel in case?

i've been reading on isolation levels 1 time again , again, lately, create sure, i'm not experienced sql server yet.

edit: should mention reason switching using readuncommitted isolation level wanted threads able commit simultaneously, optimal performance.

sql-server isolation-level

Comments

Popular posts from this blog

web services - java.lang.NoClassDefFoundError: Could not initialize class net.sf.cglib.proxy.Enhancer -

Accessing MATLAB's unicode strings from C -

javascript - mongodb won't find my schema method in nested container -