Jeff Moden - Saturday, February 17, 2018 4:11 PM
ColA would be Identity, but there could still be gaps (rollback on error, etc).
Let me explain the original problem:
Users could click many times, not realizing they were updating the item over and over (bad latency protection, I know). Each one of those updates caused a history snapshot in a history table (simulated in the table in my original post). Since the users are paid by the click, you can see the problem. I need to remove repetitive rows, indicated by exact ColC-D-E rows, in sequence one after another, with no changes in between, grouped by ColB. Column A is the IDENTITY pk.
I believe the solution put forth by Jacob Wilkins satisfies the goal.