Lowell (4/19/2013)
could it be someone was cleaning up data and used a REPLACE without a WHERE statement?the rowversion gets incrmeneted even thought here was no "real" change:
Looks like doing something stupid like running an update and setting a field to the value that already exists does this too, I'm bugging my devs more, but of course no one wants to fess up.