I am most appreciative of the offer to help from Kirk and additional input from Donald.  I will also investigate the alternative method suggested by Donald for handling my work load. 

There is no such thing as “a short schedule” and I am on a deadline.

The purpose of these sites is to share ideas, issues, and problems and seek solutions, and that was all I was trying to do.  What better help could I get than from two of Microsoft’s top people on the product in question?  Could I have possibly have reached a better audience?

I privately messaged Kirk on Friday to let him know that I am glad to supply all of the details.  I have discovered that at least part of the problem was self-inflicted.  There was a schema change in the destination database that was made directly to the data type of one column, and not to the other.

So with a bit of egg on my face I will provide all of the details.  There were four rows that failed, and three were on the erroneous column, while one was on the correct data type.  The failures were not graceful, and the error messages were not clear (or even defined).  Even if it was “operator error” it did not work right for this user.

Egg or no egg, I still seek resolution.  It is my intention to write a follow-up article on how it works out.  I like writing, and I hope that the audience likes reading; but my job comes first, of course, and my packages must get written now.

Stay tuned to this channel!