For readability's sake if nothing else, I would probably wrap the RowNumber in a CTE and delete from there. It might even be more efficient, especially in the second...

Paul White (11/18/2009)

---

It wouldn't work at all. A computed column based on a function that does data access cannot be persisted. An indexed view wouldn't work either, for...

Paul White (11/17/2009)

---

No worries 🙂

Matt Miller (#4) (11/17/2009)

---

I think there's...

Paul White (11/14/2009)

---

sqlservercentralitgeekry (11/14/2009)

---

Hugo's method depends on unique, consecutive integers, and it will fail in the event that an implementation uses a non-unique order by clause. ROW_NUMBER() solves this...

Really interesting discussion guys. I do have one complaint about Hugo's alternative method, though.

Here in the relevant bit from Hugo's code.

INSERT INTO @Results(AccountID, Date, TransactionDetailID, Amount,

...