When executing an Integrator job that writes data to a database with limited user permissions in that database, it could happen that the job does not complete successfully because some write actions fail (due to missing permissions of the user). If in that case some other write actions were already executed, the database could be in an inconsistent (and maybe unknown) state. This represents an unacceptable risk.
A solution to this problem could be to develop a roll-back mechanism for the case of a job execution failure.
This would help for all situation where the Integrator fails after writing only partially to a database (not only when it is caused by limited user permission).
Side info: In relational databases, this is often solved by using transactions (transactional mode) (see e.g. https://en.wikipedia.org/wiki/Database_transaction).
