We use sql server 2012 web on our web server and we time races. Some races are fairly large and some days we have multiple races going on at a time. Currently we time the race with software a copy of the db on our local machines and then upload the results to the web. Occasionally we return an error message during times of high traffic that locks one transaction as the "victim" when uploading data to the web. Is there a way to minimize this from happening. I am wondering about some good database design practices or a way to give one transaction priority over others.
I know this is a very vague question but any insight would be much appreciated. If I get some general responses that I think would apply to our situation I will flesh those out with further questions.
Occasionally we return an error message during times of high traffic that locks one transaction as the "victim" when uploading data to the web.This is typically a deadlock (https://technet.microsoft.com/en-us/library/ms177433(v=sql.105).aspx)