Interested to Buy Any Domain ? << Click Here >> for more details...
How do you handle data concurrency in .NET ?
- 9 Answers
- 21591 Views
- Infogain, SunGard, I also Faced
- E-Mail Answers
Answer Posted / sureshsamatham
ADO.NET and Visual Studio use optimistic concurrency,
because the data architecture is based on disconnected data.
Therefore, you need to add business logic to resolve issues
with optimistic concurrency.
(1.optimistic 2.pessimistic 3.Last in wins)
If you choose to use optimistic concurrency, there are two
general ways to determine if changes have occurred: the
version approach (true version numbers or date-time stamps)
and the saving-all-values approach.
The Version Number Approach
In the version number approach, the record to be updated
must have a column that contains a date-time stamp or
version number. The date-time stamp or a version number is
saved on the client when the record is read. This value is
then made part of the update.
One way to handle concurrency is to update only if value in
the WHERE clause matches the value on the record. The SQL
representation of this approach is:
Copy Code
UPDATE Table1 SET Column1 = @newvalue1, Column2 = @newvalue2
WHERE DateTimeStamp = @origDateTimeStamp
Alternatively, the comparison can be made using the version
number:
Copy Code
UPDATE Table1 SET Column1 = @newvalue1, Column2 = @newvalue2
WHERE RowVersion = @origRowVersionValue
If the date-time stamps or version numbers match, the record
in the data store has not changed and can be safely updated
with the new values from the dataset. An error is returned
if they don't match. You can write code to implement this
form of concurrency checking in Visual Studio. You will also
have to write code to respond to any update conflicts. To
keep the date-time stamp or version number accurate, you
need to set up a trigger on the table to update it when a
change to a row occurs.
The Saving-All-Values Approach
An alternative to using a date-time stamp or version number
is to get copies of all the fields when the record is read.
The DataSet object in ADO.NET maintains two versions of each
modified record: an original version (that was originally
read from the data source) and a modified version,
representing the user updates. When attempting to write the
record back to the data source, the original values in the
data row are compared against the record in the data source.
If they match, it means that the database record has not
changed since it was read. In that case, the changed values
from the dataset are successfully written to the database.
Each data adapter command has a parameters collection for
each of its four commands (DELETE, INSERT, SELECT, and
UPDATE). Each command has parameters for both the original
values, as well as the current (or modified) values.
Note: use time stamps to avoid concurrency violations
| Is This Answer Correct ? | 6 Yes | 0 No |
Post New Answer View All Answers
What is ado.net object model?
What is ado or jdbc?
What is full form of ado?
How to enable and disable connection pooling?
What are the classes in System.Data.Common Namespace?
Explain the different row versions available in table?
What two types of data providers does ADO.NET supply? What determines which one you should use?
Explain ado.net features?
What are the different ado.net namespaces are available in .net?
How can we check that some changes have been made to dataset since it was loaded?
Which method in OLEDBAdapter is used to populate dataset with records?
What is ado object model?
What is ambient transaction?
How to load multiple tables into a dataset?
If we are not returning any records from the database, which method is to be used?
