Query Diff Documentation
Overview
Query Diff in DataDios helps you validate data after migration by comparing query results from your source and target systems. This ensures that your data has been migrated accurately and consistently.
Stages of Query Diff
- Locate Query Diff in DataDios
- Create or import the required Data Sources
- Define and select Key Columns for verification
- Process the data sources
- View summary and compare differences
Steps to Perform Query Diff
Step 1: Navigate to Query Diff
-
Go to the Smart Diff tab in DataDios
-
Click on Query Diff

-
Click Create Diff → This will open the Source and Target Data Source Selection page
On this page, you can:
-
Switch from Datasource Diff (default) to Query Diff
-

-
Define your workflow name or diff job name
-
Add a description
-
Select Source and Target Data Sources

Step 2: Add Queries
-
Select your data sources and click Next
-
Add queries for both Source and Target
Ensure queries are validated before adding
-
Click Next

Step 3: Analyse Step
-
The Analyse step automatically maps matching columns between queries
-
Review the mapping
-
Select the Key Columns to be used in comparison

Step 4: Execute Stage
-
Select the Key Columns that may differ across the two data sources
-
(Optional) Schedule your workflow by clicking Schedule Workflow
-
Click Next to start execution and view diff results

Step 5: Diff Summary
-
Wait for the diff process to complete (time varies by dataset size)
-
Once complete, review the Diff Overview

-
Click View Diff to explore detailed differences
Types of Diffs:
-
Metadata Diff Shows differences between the structure (columns) of your queries

-
Data Diff Shows row-level differences in query results

Workflow Actions
Once a Query Diff workflow has completed, three additional actions are available from the Workflows list page. These let you inspect, re-run, or duplicate any finished workflow.

Stepper Flow (Reference)
Every Query Diff workflow follows a 4-step process. The table below is referenced throughout the action descriptions.
| Step | Name | Purpose |
|---|---|---|
| 0 | Select Data Source | Choose source/target data sources, set job name |
| 1 | Analyze | Write or edit source/target SQL queries per pair |
| 2 | Column Mapping | Map columns between source and target, set keys |
| 3 | View Diff | Execute (or view) the diff and inspect results |
1. View Info
Icon: Eye Purpose: Inspect all details of a completed workflow without modifying anything.

What Happens
- The system fetches the workflow's completed step data from the backend.
- Navigates to the Query Diff page with read-only permissions.
- The form renders in fully read-only mode — every input, dropdown, editor, and button is disabled.
Step 0 — Select Data Source
- Source and target data sources are displayed as selected but not changeable.
- Job name and description are shown but not editable.
- Connection test is skipped — connections are marked as "connected" automatically.
Step 1 — Analyze
- Source and target SQL queries are shown in the editor, not editable.
- The sidebar displays data source names as plain text instead of the interactive object tree.
- Queries cannot be added, removed, or modified.
- Hovering over disabled elements shows: "This query is view only. Update access is not available."
Step 2 — Column Mapping
- Column mappings and primary key selections are displayed from cached results.
- No API call is made to re-analyze queries — data comes from the stored step results.
- Columns, keys, and query pair names are all non-editable.
Step 3 — View Diff
- Diff results are fetched from stored data, not re-executed.
- No "Stop" button is shown.
- Summary and detailed diff views are available for browsing.
Navigation
- Forward: The "Next" button advances through steps up to the number of steps that were actually completed in the original workflow. You cannot advance beyond what was completed.
- Backward: The "Back" button is enabled for steps 1, 2, and 3.
- No "Start Over": Once you reach the last completed step, the Next button is disabled.
2. Run Details
Icon: Play Purpose: Re-run the diff for a completed workflow using its existing configuration.

What Happens
- The system fetches the workflow's completed step data.
- A new sync workflow is created on the backend, linked to the original workflow.
- The user lands directly on Step 3 (View Diff) — Steps 0–2 are skipped entirely.