When RRS URs are coordinated under a single transactional scope by distributed protocols that use the distributed syncpoint resource manager (DSRM) or server distributed syncpoint manager (SDSRM) roles, RRS is required to log separate in-doubt records for each of the URs except the initiating one. However, RRS manages all of the URs in a cascaded UR family as if the family was a single UR. There is no need for cascaded URs to go in-doubt, or be logged separately. If the top-level UR does not have a DSRM or SDSRM role, RRS can immediately make the commit or backout decision for the UR family and log only those records needed to record the final outcome of the cascaded transaction. If the top-level UR has a RM which has taken the DSRM or SDSRM role, RRS will have to log an in-doubt record, but it will still only have to log one in-doubt record for the entire cascaded UR family.

Prior to the existence of cascaded transactions, RRS restricted the amount of data that could be logged for a single transaction to a single System Logger log block, 64K of data. While all of the data for a single UR must still fit within a single log block, RRS allows data for cascaded UR families to span multiple log blocks.