Hi
Every now and then I run into cases where I'm doing a bulk copy and the it is terminated with an exception due to some primary key violation, foreign key violation, constraint violation, etc.
The violations are valid and need to be looked into, but what I can't figure out is why the DataTable or DataSet I'm using for the bulk copy never has the HasErrors property turned on when these exceptions occur. If it was on, I could drilldown to the individual DataRow that has the HasErrors flag turned on and quickly find the source of the problem.
A search on the net yelded very few answers on this. Looks like it is not even possible.
Anyone else ever run into this? Is it perhaps something you configure on SQL Server? I'm using SQL Server 2005, btw, and framework 3.5.
Thx!
MuadDubbby
Every now and then I run into cases where I'm doing a bulk copy and the it is terminated with an exception due to some primary key violation, foreign key violation, constraint violation, etc.
The violations are valid and need to be looked into, but what I can't figure out is why the DataTable or DataSet I'm using for the bulk copy never has the HasErrors property turned on when these exceptions occur. If it was on, I could drilldown to the individual DataRow that has the HasErrors flag turned on and quickly find the source of the problem.
A search on the net yelded very few answers on this. Looks like it is not even possible.
Anyone else ever run into this? Is it perhaps something you configure on SQL Server? I'm using SQL Server 2005, btw, and framework 3.5.
Thx!
MuadDubbby