ADO.NET, SQL Server, and concurrency issues

  • Thread starter Thread starter Leszek
  • Start date Start date
L

Leszek

Hello,

I have a question regarding concurency issues using ADO.NET and SQL Server.
Does ADO.NET provide any specific support to resolve concurrency conficts in
a multiuser environment? How should I deal with the situation when we have
multiple ASP.NET clients trying to modify the same record?

Thanks for any suggestions,
Leszek Taratuta
 
If you are using a CommandBuilder, you have limited ability to specify
concurrency type. You can turn off OPtimistic COncurrency in the
DataAdapter configuration wizard depending on how you want to handle things.
Another approach is to let it throw a concurrency exception and then trap
that exception. You can prompt the user from there asking hwo they want to
handle the exception and just have some branch logic. I can't do the entire
subject in this post, but if you check this link at MSDN, it tells you your
options as well as how to possibly handle them.
http://msdn.microsoft.com/library/d...us/vbcon/html/vboridataupdatesconcurrency.asp

HTH,

Bill
 
Great!
Thanks for information.

Leszek Taratuta

William Ryan said:
If you are using a CommandBuilder, you have limited ability to specify
concurrency type. You can turn off OPtimistic COncurrency in the
DataAdapter configuration wizard depending on how you want to handle things.
Another approach is to let it throw a concurrency exception and then trap
that exception. You can prompt the user from there asking hwo they want to
handle the exception and just have some branch logic. I can't do the entire
subject in this post, but if you check this link at MSDN, it tells you your
options as well as how to possibly handle them.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/
vboridataupdatesconcurrency.asp

HTH,

Bill
conficts
Click to expand...
 
Back
Top