When comparing a small number of tables across different databases in a cloud deployment for large schemas that are not of our design, Data Comparison performs poorly in the transition from Options to Mapping. In some cases, it exceeds the allowed timeout for schemas with thousands of objects in both the source and target.

Observationally, even if the Optional "include" filter mask is used, Data Comparison is describing all data objects in both schemas. The only thing actually filtered is the result set displayed in the Mapping.

It would therefore seem simple to limit the objects enumerated and described in each schema by the include mask. That should yield a stunning performance improvement in this phase of the data comparison operation.