views:

36

answers:

1

I am developing a set of applications that all hit the same database, and concurrency has been one of the biggest issues I've had to deal with.

I'm developing solutions to work around these issues, and I recently thought of using SQL queries instead of LINQ queries to update databases. Because SQL has pessimistic concurrency control, in terms of preventing concurrency issues, is this a good and simple solution to my LINQ concurrency woes?

+1  A: 

Linq just passes SQL statements to SQL Server. So it could very well be sending SQL Server the same statements you would be generating. And besides, SQL Server uses optimistic concurrency. So I think you have other issues.

Randy Minder
and so, just using SQL really doesn't make any positive difference....
marc_s
@marc_s - Using SQL or Linq wouldn't make any difference, IMO.
Randy Minder