QuestionQ28

Performance Optimization, Querying & Transformation

A dashboard query is executing far more slowly than expected. Query Profile indicates that a join operator consumes 70% of total execution time and produces 1,000 times more rows than its input tables.

What is causing this problem?

Explanation

An exploding join occurs when a missing or incorrect ON condition allows unintended combinations of rows, potentially creating a Cartesian product. It produces orders of magnitude more output rows than its inputs and can make the join operator consume most of the execution time.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!