Our users go through a series of editing views to update attribution on tables as well as create and update geometries for feature classes. When they're finished with the process, we need to save all of those updates as a transaction otherwise we risk corrupting our database. We don't use esri relationship classes but we do have relationships in our database that we must maintain. In our largest workflow, we have 5 tables and one feature class that all need to be saved at the same time, as one transaction.
