Another very important article in the SQL Series: Identifying Duplicate Transactions.
This is very much important and much needed one for all those developers/consultants. The basic idea is to identify unwanted, duplicate records on any transaction tables.
While David has mentioned the need of this, I would like to add one more point to stress the importance of having this script: Most of the customizations written across the world create records directly on the transaction tables (any module that matters). Even if we think that this is going to be perfect on most of the times, there is still a probability of a record getting inserted on any of the table without any relevance.
I would also like to derive a script, which can list the orphaned records as well as the craps. Well, that’s not so easy, I understand. But would be a great script.