Hi Ninja's_RGR'us,

No. As far as I know, UPDATE is not quirky at all in SQL Server 2000. What do you mean by "quirky update"?

What I was refering too is the lack of ROW_NUMBER() in SQL Server 2000. This means you'll either have to take your chance with IDENTITY, at the risk of gaps, as the author of this article did; or you have to use a correlated subquery to calculate the row number on the fly, which can result in dramatic performance as the amount of rows grows. Plus, the queries tend to get long and hard to understand.