Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dadunn
Yak Posting Veteran
67 Posts |
 Posted - 2001-07-17 : 19:29:54
|
| I have a Warehouse Management system to which I do not own the code.When performing a "Receive All" on a receipt, the program updates the received_qty and Open_qty in the receipt_detail table on each row (line) one by one.This works fine for small orders, but these orders are 1100 lines and it takes more than 15 minutes to update every single line.The developers have created some Access interfaces that do some very similar row by row updates.Run together, my processor utilization sits at 75% on all four processors for 20 minutes.The users are getting deadlock conditions trying to query the receipt_detail table at the same time these queries are running.The Isolation Level is currently set to Read Committed. Would it make sense to change this to Read Uncommitted to relieve the deadlocks?Is there any danger to my data by doing this?Dave |
|
|
|
|
|
Isolation Level