When I upload race results periodically throughout a large running or biking race, people who have already finished are often accessing those same results. What often happens is that they get a transaction error. I have recently been directed to the NOLOCK hint as a way to avoid those errors. I assume that I would put that in the query or stored procedure that generates the results display for the participant who is trying to view results.
It is my understanding that this may generate an incomplete results display but that the upload of new data from my end will not be affected. Is that correct? If not, what else could happen? If it is correct, would that mean no 500 error would be generated? Just trying to get a grip on how to best upload results data without encountering errors as people are trying to access that data.
BTW, our local timers have sql server 2012 express on their local machines when they time the race, but our web server is running slq ser 2012 web version.
Thanks in advance for any assistamnce!