Posted by Erland Sommarskog on 06/25/05 00:50

xAvailx (bjzamora@hotmail.com) writes:
> Below is the DDL, DML and a Stored Proc demonstrating the approach. I
> am using a rowversion column for concurrency checking. Another approach
> that is less intrusive (doesn't require having a rowversion column in
> all tables) is using checksum. I may eventually use checksum but the
> process flow should be almost identical.

I would advice against using checksum. The checksum functions in SQL Server
are simple XOR, and the probability that two different rows are not
detected is not negligible.

rowversion is fine.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

• Next in forum: Re: OpenQuery and passing variables
• Prev in forum: Re: Problem with script
• Thread view: Re: Concurrency Handling In Stored Procedures

[Reply to this message]