Timestamp versus Original-Version

  • Thread starter Thread starter Limberger Florian
  • Start date Start date
L

Limberger Florian

Till now i have used the original-version of the data in my dataset to check
wether a different user has changed the data (optimistic concurrency).
Now I encountered that it might be more intelligent to do it with
timestamping (within stored procedures).
Are there any drawbacks of using timestamping?
The advantage (in my opinion) is that the number of parameters sent over the
network to the database is decreased.

thanks
Flo
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Optimistic Concurrency and TimeStamp 4
Using a Timestamp field to implement optimistic concurrency 2
Dataset timestamp fails to update 1
dbdirect methods with timestamp columns 2
Convert sql2000 timestamp field 4
C# timestamp datatype? 3
Retrieving timestamp output parameter from SqlCommand 5
Error: Executing Stored Procedures-- Cannot Pass TimeStamp Values From sqlCommand Object Parameter 3

Back
Top