Review table pairs before reconciliation starts.
Table mapping turns schema pairs into concrete comparison targets. Compare suggests source and target table pairs automatically, but the view is designed for quick review, manual correction, and activation of only the pairs that should actually run.
How table mapping is built
The system analyzes the schema pairs defined earlier and proposes table pairs according to the selected matching rules. The result is a review table that can be confirmed as-is or refined before execution.
Each matched schema combination becomes a candidate space for table pairing.
Patterns such as LIKE rules help Compare align source and target table names.
Users can validate the suggestions, unselect pairs, or manually adjust the target side.
Only the confirmed pairs move forward into deeper validation and advanced configuration.
Mapping state signals
The table mapping grid exposes a compact state machine. Color is only the transport layer. The actual signal is whether the row already has a resolved source-target binding or still requires operator review.
Automatic matching produced a concrete source table and target table pair. The row can move forward into validation, column review, and advanced configuration.
finance.accounts = archive.accountsUI rendering: purple row marker for a resolved pair.The matcher did not produce a trustworthy final binding. The row is incomplete, ambiguous, or structurally suspicious and should be reviewed before execution.
finance.accounts = ?UI rendering: amber row marker for a pair that is not execution-ready.What each column means
Generated automatically in the form source_schema=target_schema. Repeated schema
pairs receive a numeric suffix such as (2) or (3).
Displays the table coming from the selected source schema. It represents the left side of the comparison pair.
Displays the proposed target table. If the automatic match is not the right one, it can be adjusted manually.
Controls how columns are included or excluded inside the paired tables, either by exact names
or wildcard patterns with LIKE and NOT LIKE.
Legacy naming Automatic matching can misread old prefixes, suffixes, or parallel naming schemes.
Partial scopes Some tables should stay out of the run even if their names match correctly.
Business context The technically closest match is not always the operationally correct comparison target.
Interface helpers
When enabled, selecting the target table automatically marks the whole pair as active for reconciliation. This removes one extra confirmation step during bulk setup.
Expands the table list to make large mapping sets easier to review. It is especially useful when complex schemas produce many candidate pairs.