Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan
Compare Expected vs Actual After Migration
00:00
5 left

Compare Expected vs Actual After Migration

HardSQL · PostgreSQL

Problem

Write a SQL query to compare expected versus actual data after a migration.

Compare every record key in the expected and actual datasets. The result should identify matching records, changed values, records missing from the actual dataset, and unexpected actual records. Comparisons must treat two NULL values as equal.

Output

  1. One row per distinct record key.
  2. Columns: record_key, expected and actual values, and comparison_result.
  3. Include match, mismatch, missing_actual, and unexpected_actual results.
  4. Order by record_key ascending.

Schema

expected_migration
ColumnTypeDescription
record_keyPKVARCHAR(20)Stable identifier expected after migration
statusVARCHAR(20)Expected record status
amountNUMERIC(12,2)Expected monetary value
updated_atDATEExpected last update date
actual_migration
ColumnTypeDescription
record_keyPKVARCHAR(20)Stable identifier produced by migration
statusVARCHAR(20)Actual migrated record status
amountNUMERIC(12,2)Actual migrated monetary value
updated_atDATEActual migrated last update date
Tablesexpected_migrationactual_migration
Interviewer

Your question is Compare Expected vs Actual After Migration. Start with the requirements and the two tables in the Question tab.

Run and submit as often as you like. When you're ready, talk me through your approach or go straight to the code.

You need to log in / sign up to run or submit.
CodePostgreSQL
Sign up free to run your codeLog inLn 1
Run your query to see results here.