Reviewed by Aditya Kumar · Last reviewed 2026-03-24
CROSS JOIN: cartesian product, every row of A with every row of B. No ON clause. Use for: combinations (all pairs), expanding dimensions. Dangerous on large tables—N*M rows. Example: SELECT * FROM sizes CROSS JOIN colors. For limited cross: add WHERE to filter. Or use for...
CROSS JOIN: cartesian product, every row of A with every row of B. No ON clause. Use for: combinations (all pairs), expanding dimensions. Dangerous on large tables—NM rows. Example: SELECT FROM sizes CROSS JOIN colors. For limited cross: add WHERE to filter. Or use for generating sequences. Why it matters: Design choices compound at scale—wrong approach can cause 100× overhead. Scalability trade-offs: Profile before optimizing; validate on sample then full. Cost implications: Suboptimal choices multiply at billion-row scale.
Red Flag: Generic textbook answers. Pro-Move: 'At scale we measured X, implemented Y, achieved Z%—validated and iterated.'
According to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.