You are probably done a lot work with ms sql server.
Although it is possible specify number of rows to skip the there is no point of doing it
I do not know why you want it, from my point of view the best thing is to write a message into the log and
carry on.
The implementation depends on the target database.
Data can be loaded as part of one big transaction and in case of error the whole transaction will be rolled back,
Or in batches so the batch will be rolled back (for sql server)
or record by record insert record, commit, insert record, commit for(ODBC,OleDB)
It is slightly different for Oracle,Interbase,MySql and PostgreSQL and it is user definable.
For every data target the best possible way of loading the data used
Mike
