In such case, it is clear that the total data set should not be the transactional boundary, but rather that each employee record is such a boundary. If employee A fails to be imported/updated (e.g.

A common SQL habit is to use SELECT * on a query, because it’s tedious to list all the columns you need. Plus, sometimes those columns may change over time, so why not just do things the easy way? But ...