Finding Primary Key Violations

Recently I've been processing lots of legacy DBase files into Sql Server 2005 via SqlBulkCopy.

However, before I import the records (tens of thousands) there is a need to find, then handle the legacy DBase records that will cause a Sql Server primary key violation (if any).

Karen Gayda's solution works like a charm:

http://www.sqlteam.com/article/anticipating-primary-key-violations

IMPORTANT: SqlBulkCopy has a column mapper feature. However, only key columns should be included in select parameter - @vcSelectStatement. If source table columns are named differently than in the target then they must be aliased with the same name as the target. These restrictions were necessary to make the procedure generic.