What is the purpose of intermediate tables in query design?

• A. Use intermediate tables to divide a query into smaller queries that write results to holding tables, then unite final results
• B. Avoid intermediate tables and use a single large query
• C. Replacing data views with intermediate tables
• D. Intermediate tables are only for archival storage

Answer: (A)

Dividing a complex query into manageable steps by creating intermediate (holding) tables that store the results of each step is the key idea. This approach lets you test and tune each part separately, then combine the staged results in a final query. It also can improve performance by materializing expensive computations rather than recalculating them in one long pass, and it makes debugging easier since you can inspect data after each stage and reuse partial results for different outcomes. The described pattern—split the work, write each stage to holding tables, then unite them at the end—captures the purpose of intermediate tables. Using a single large query is harder to maintain and optimize, replacing views with intermediate tables isn’t the main aim, and intermediate tables aren’t solely for archival storage.