Dataford
Interview QuestionsInterview GuidesExperiencesMock InterviewsPricing
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 feedbackSuccess 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
Join Strategy: Merge vs Hash
00:00
5 left

Join Strategy: Merge vs Hash

HardSQL · PostgreSQL

Problem

Explain the difference between a merge join and a hash join in SQL Server, and when the optimizer would choose each based on sorted inputs, memory use, and data volume.

Use the provided PostgreSQL tables to demonstrate the joined result, then explain how the optimizer may choose between these strategies. Discuss how sorted inputs, indexes, cardinality, and insufficient memory affect the plan.

Output

  1. Return one row per matching pair, with join_key, left_row_id, right_row_id, and left_value.
  2. Include only rows with matching non-NULL keys.
  3. Order by join_key, left_row_id, and right_row_id ascending.

Schema

left_input
ColumnTypeDescription
row_idPKINTUnique identifier for the left input row
join_keyINTNullable equality join key
valueVARCHAR(50)Value associated with the left input row
right_input
ColumnTypeDescription
row_idPKINTUnique identifier for the right input row
join_keyINTNullable equality join key
valueVARCHAR(50)Value associated with the right input row
Tablesleft_inputright_input
Interviewer

Your question is Join Strategy: Merge vs Hash. 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.