Viewing 10 posts - 1 through 10 (of 10 total)
I have fixed this problem.
There were duplicate keys being inserted into the primary key column, but the data was not making it into the error output. The duplicate keys...
October 25, 2010 at 4:25 am
Hi,
Yes, the primary key GUIDs are in the Excel file.
Each time the insert is attempted a new random set of GUIDs are generated using NewID(). Each new set is...
October 19, 2010 at 1:47 am
All the data under Error Output is rejected, on the second pass.
The Error Output data is a result of re-directing the erroneous data, on a fail condition.
October 18, 2010 at 8:42 am
Hi,
Thanks for the interest.
Please read the first post, in that I attempt to explain what the problem is.
It's pretty complicated, but my database has the wrong collation property set on...
October 18, 2010 at 8:17 am
Hi,
Thanks for the interest. The attached Excel doc has an error output, and the affending rows are there.
As can be seen, the Primary key column (newGiud) does not have...
October 18, 2010 at 3:03 am
Hi,
Thanks for the interest. The attached Excel doc has an error output, and the affending rows are there.
As can be seen, the Primary key column (newGiud) does not have...
October 18, 2010 at 2:20 am
I'll give your suggestions a try.
I'll be back !!
October 15, 2010 at 4:37 am
That's the Error Output section in the Excel file.
The package runs fine with the error handling in it, but the consuming C# app does not display any data, so I...
October 15, 2010 at 4:15 am
Hi,
Thanks for the interest.
I've done all that. The database is populated before it fails.
I have included a copy of the data in Excel form. Definately no duplicates in...
October 15, 2010 at 4:07 am
Not directly, only through foreign key constraints.
That being the case I would expect the error to be a foreign key constraint problem, not a primary key constraint problem.
October 15, 2010 at 3:15 am
Viewing 10 posts - 1 through 10 (of 10 total)