sql server - t-sql possible deadlock solution -
i running time taking (few hours) procedure, doing inserts, updates selects. there possibility make lowest possible locking on used data? think got deadlock problem here when other procedures tries selects on data.
i love make insert/delete/update statements in procedure using select on big table date not block data in way (or maybe @ least not selects).
would using set transaction isolation level read uncommitted
solve problem? read snapshots, database big set on.
yes, using set transaction isolation level read uncommitted
@ top of each query batch solve issue of deadlocks. keep in mind these dirty reads, in not reading "committed" transactions when using setting. use statement lot avoid causing deadlock issues in production environments high traffic database tables.
read full list of pros & cons of using read uncommitted
here: http://sqlblog.com/blogs/tamarick_hill/archive/2013/05/06/pros-cons-of-using-read-uncommitted-and-nolock.aspx
Comments
Post a Comment