I have a scenario where I have to update multiple rows in a table using a SQL Server stored procedure.
I am using threading to make updates fast (C# console application + ADO.NET).
Each thread will update different row set from that table.
I am curious about that will it cause any deadlocks in SQL?
More Details:
I have independent threads and they do not share any common resources. I am more worried about SQL locking mechanism as multiple threads are calling same Stored Proc to update same table but different record sets (different rows).
It should not cause any deadlocks (as long as there are no strange and complicated constraints).
It could cause delays where the threads have to wait for each other when you use heavy TransIsolation like snapshot. But with the default ReadCommitted you should be OK.