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 |
|
cathal
Starting Member
4 Posts |
 Posted - 2003-04-28 : 12:42:29
|
| Hello,I have a multiuser factory floor system. Multiple workers scan in barcodes, and the data is stored on their local machines in an msde instance.When a batch is finished this data is pushed up to the main sql server 2000 box. Another application reads from this same database to establish the batch details, and then uses this data as the next part of its workflow. The system works well mostly, but lately I've had some data issues.My problem is that occasionally, whilst under heavy load, when I try to read from the main sql 2000 box, an update is still going on, and so my read fails. I'm looking for advice on how to best deal with this. Obviously, I could write application code to either retry a number of times, or pop-up a retry/cancel dialog for the user, but it was suggested to me that setting transaction isolation levels and table locking hints might be a better option.Any advice would be much appreciated.Cathal |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-04-28 : 12:52:57
|
| Have you tried:SELECT * FROM myTABLE (NOLOCK)Brett8-) |
 |
|
|
|
|
|
locking and concurrency issues