Please note that dbForge performs mapping identically to Red Gate.

Once automapping is performed and the user specified objects are excluded from the mapping, you can perform comparison and then save it. When you open the save comparison, the previously saved user specified mapping gets restored. Such a behavior is also identical to the Red Gate’s one.

If you perform automapping, exclude specific objects from the mapping, perform comparison, save, then close the document, make changes in Source and Target by removing the pair of the mapped tables and then adding the pair of new tables, then open the saved project, the saved mapping gets restored where possible. That is, the removed pair of the tables is excluded from the mapping. For the rest, the mapping is restored and the new pair of tables is mapped automatically. Such a behavior is also identical to the Red Gate’s one.

Additionally, starting from version 6.2, there will be implemented the pair of the options in the comparison wizard of dbForge. These are the ‘Include/Exclude Tables or Views by mask’ options allowing you to define the mask or specific object names to restrict automatic mapping. You will be able to save the state of the options in order to use by default.

So, you can setup a *.dcomp data comparison document and save it. Next time you work with the databases, you can use the previously saved *.dcomp file. Automatic mapping will get restored.