title: Concurrent updates on the same table from different servers for different records
body: <p>As far I read from this forum, its understood that there may not be any issue in a design like this. But wanted to be in the safe side.  </p>
  
  <p>I have a simple update query as below which has to be executed in a server (Lets say Master server): </p>
  
  <pre><code>update TempTable set [TempCol_1] = 'Value_1' 
  where TempTable.[ TempCol_2] = ‘Server_1’
  </code></pre>
  
  <p>The <strong>'Value_1'</strong> and <strong>'Server_1’</strong> are variable fields. This same query has to be run from different servers.<br>
  For example, when this query is being executed from ‘server-1’ , <strong>where TempTable.[ TempCol_2] = ‘Server_1’</strong><br>
  when this query is being executed from ‘server-2’
  <strong>where TempTable.[ TempCol_2] = ‘Server_2’</strong> and so on. </p>
  
  <p>It means, even if there are concurrent updates on the same table in the master server, the where condition will remain different for each server and from each server, <strong>at a given time</strong>, there will be only one execution of the query. </p>
  
  <p>While designing this scenario, should we be worried about table locks or any other lock/transaction issue on the table in the master server (i.e TempTable) ??  Will the table be open to update at the same time from different servers or will it wait for the first triggered updation to complete and makes the second triggered updation is some sort of queue or somethng??</p>