SqlBulkCopy - Improve granularity of exceptions due to data mismatches.

[Korporal]

Is your feature request related to a problem? Please describe.

When we call SqlBulkCopy.WriteToServer and there are rows that lead to insert exceptions (data lengths etc) the exception we see contains no information about the row number of the column.

Describe the solution you'd like

Report the row number and the column name in addition to the details of the mismatch.

Describe alternatives you've considered

Writing our own pre-validator.

Additional context

In one case we were attempting to insert 1,700,000 rows and we know that some column in some row was a problem but could not pin it down.

[cheenamalhotra]

Hi @Korporal

We have addressed your concern in PR #437 and v2.0.0-preview2 contains this enhancement.
Please give that a try and let us know.

[cheenamalhotra]

Closing due to inactivity and support provided with recent driver updates.

[Korporal]

@cheenamalhotra Thanks for the effort put into this, very helpful change and I look forward to leveraging very soon!

[Korporal]

@cheenamalhotra The app that was experiencing the original problem is built on .Net Framework 4.5.2 is this something we'll see as an update to .Net Framework or is it all .Net Core these days?

[cheenamalhotra]

Microsoft.Data.SqlClient supports .NET Framework 4.6+ and the above PR also applies to the same.
We aim to provide fixes/improvements to .NET Framework target applications equally as .NET Core and Standard for smoother transition experience.