Prepare comparable values
Copy the expected values from the Release source and the actual values from SQL into separate lists. Use the same business key on both sides—for example employee ID, role name or configuration code—rather than comparing full rows that contain changing timestamps.
- Place one value per line.
- Remove headings unless both lists contain the same heading.
- Keep leading zeros when they are part of the identifier.
- Use the ignore-capitalization and extra-space option when those differences are not meaningful.
Read the result in the right order
Review Matched first. This confirms which expected Release values are present in SQL. Next, review values missing from SQL; these are the items that may indicate an incomplete deployment. Review SQL-only extras last, because they do not automatically mean the Release failed.
- Matched: present in both Release and SQL
- Missing from SQL: expected by Release but not found
- SQL-only: present in SQL but not listed in Release
Investigate differences safely
Do not immediately change the database based only on a comparison result. Recheck filters, environment, capitalization, whitespace and the selected key. Export or copy the missing list, confirm it against the release package and then follow the normal change process.
- Confirm that the SQL query targets the correct environment.
- Check whether duplicate SQL rows were intentionally collapsed.
- Save the comparison result with the release evidence.
- Escalate unexplained missing values before sign-off.
Try the related Docsy tools
Open the tool that matches your task, review its limitations and keep your original files until you have checked the result.