Real questions rarely involve just two tables. To report each delivery with its batsman's name, the bowler's name, the team, the venue, and the match date, you must chain several joins together in one query. Joining multiple tables is how you reassemble a fully normalised database into the rich, denormalised view a report or screen actually needs to display.
Multi-table joins are not a new mechanism; they are repeated application of the joins you already know, each connecting one more table to the growing result. The engine joins the first two tables, then joins the third to that intermediate result, and so on. Understanding this stepwise composition demystifies queries that span four or five tables and look intimidating at first glance.
The skills that matter most here are managing aliases cleanly, choosing inner versus outer joins at each link deliberately, and ordering the joins for clarity and performance. A single misjudged join type or condition in a long chain can silently distort the entire result, so disciplined multi-table joining is what makes complex reporting queries both correct and maintainable as they grow.