Comments posted to this topic are about the item Identify Primary Key Violation Prior to Insert (Updated)
For more detail on using this procedure, read the SQL Team article that I posted: http://www.sqlteam.com/article/anticipating-primary-key-violations
This gives step-by-step instructions on how to get the most out of this procedure.
What ever happened to simply grouping by the primary key with a count > 1? Wouldn't that find dupes just as well? It seems like overkill to run each record through a cursor against multiple functions.
It doesn't work in every scenario. The proc. that I wrote handles every condition possible that I had encountered.
Viewing 4 posts - 1 through 3 (of 3 total)