Hi,
I would like to know best approach for concurrent updates.
I have searched this forum and googled and came to following solutions:
1. Create a column lastupdatetime and use that disallow concurrent updates
2. Use Isolation level of Repeatable Read
For sol1, I am not sure how it will resolve concurrent updates when you are doing bulk updates. Soln presumes that you are updating record one after another(which is not true always)
Soln 2, leads to restricting locking and thus would have performance impact.
I would like to know from experienced people here how they have designed it in their applications.
My application will be a web application with high volume and thus likelyhood of concurrent updates.
Keeping this in mind, can anybody else share their thoughts regarding an optimum design for this situation.
I would like to know best approach for concurrent updates.
I have searched this forum and googled and came to following solutions:
1. Create a column lastupdatetime and use that disallow concurrent updates
2. Use Isolation level of Repeatable Read
For sol1, I am not sure how it will resolve concurrent updates when you are doing bulk updates. Soln presumes that you are updating record one after another(which is not true always)
Soln 2, leads to restricting locking and thus would have performance impact.
I would like to know from experienced people here how they have designed it in their applications.
My application will be a web application with high volume and thus likelyhood of concurrent updates.
Keeping this in mind, can anybody else share their thoughts regarding an optimum design for this situation.