Often, when building a database subset, there is a requirement to ensure that every row in certain tables is present. In other words, some tables need to be present in full in the target database even if, strictly speaking, the rows they contain are not required to support the data extracted by the driver rows. This requirement is usually true of reference tables. For example, a table of discounts needs to be present in full even if none of the other extracted rows actually require that specific discount.
All Rows rules can be added manually using the New All Rows Rule Form (discussed below). However a far better way to add All Rows rules is to use the Safe All Rows Rule Generator tool found on the Set Designer Rule Tools tab to add them in bulk. The reason it is better to use the Safe All Rows Rule Generator tool is that it will only add rules which are Safe and thus less likely to cause what is known as an extraction set explosion.
Important Note: It is strongly advised that the contents of the extraction set explosion help file be read and and understood before any All Rows Rules are added. This help file will provide valuable tips which will enable you to avoid constructing a set of rules for which the only valid referentially correct set of extracted rows is the majority of the rows in the source database.
All Rows rules execute in Stage 1 of the extraction process. The DataBee extraction process is multithreaded and can run multiple rules simultaneously. If necessary, (it usually isn't) the execution order of the All Rows rules can be explicitly controlled by adjusting the rule block component of the rule ID number. Please see the discussion of rule blocks in the extraction set overview help page in order to understand how to explicitly control the execution order of stage 1 and stage 3 extraction rules.
All Rows rules are created by launching the New All Rows Rule Form using the New Extraction Rule button located on the bottom right of the main Set Designer form.
How to Create a New All Rows Rule