You need to check dbc.QryLogStepsV (if it's enabled) to find which step failed.
It will include all steps successfully completed, so the first missing step run out of spool.
There's no product join, but some duplicated spools, you should compare actual to estimated rows to see if they're highly different. Might be due to outdated stats (there's a lot of "high confidence")
You need to check dbc.QryLogStepsV (if it's enabled) to find which step failed.
It will include all steps successfully completed, so the first missing step run out of spool.
There's no product join, but some duplicated spools, you should compare actual to estimated rows to see if they're highly different. Might be due to outdated stats (there's a lot of "high confidence")
Dieter