I am writing a high performance win32 telemetry midleware service which uploads to SQL server in bulk frequently. I know how to do simple things in ODBC native-client.
ODBC native-client documentation is terse to say the least. I would like to know from people who have used the native client bulk upload feature what the behaviour of a bulk upload is when one of the rows causes a server-side constraint error.
Specifically:
- Do the drivers respond with the row that fails,
- if it does, do previously inserted rows get rolled back or can you remove the erroneous row and resume the bulk upload?
If the above doesn't make sense should I look at the ole DB api. It looks like it has higher levels of abstraction as other COM api's it looks horendously bloated and terse.