sql server - Preventing SQL deadlocks when database is updated by two different processes -


we have system 2 different processes update same sql server tables. 1 process has high transaction volume , initiated scheduled task runs 24 x 7. other low transaction volume process initiated user volume. second process database transactions being killed because of deadlocks. i'm not sure how fix this. ideally, want user instantiated transactions have priority , scheduled task transactions wait until database free.

well us, solution change isolation level read committed read comitted snapshot. cause selects snapshot table reading before doing select. prevents selects colliding each other causing deadlock alternative have been use (nolock) query hints on select statements. however, have lot of sql , looking @ rewriting lot of code. changing isolation level easy , quick , did not require lot of regression testing.


Comments

Popular posts from this blog

How to provide Authorization & Authentication using Asp.net, C#? -

toolbar - How to add link to user registration inside toobar in admin joomla 3 custom component -

How to use Authorization & Authentication in Asp.net, C#? -