February 13, 2018 at 10:33 am
https://www.brentozar.com/pastetheplan/?id=H1rMn9evM
The second nested loop is warning that there is no join predicate. I'm still new to this so I'm confused. Is that because I am using a CTE to determine the values for two of the attributes? This presentation table is used in more that a few reports, and I don't want to create a second one for this very unique one.
Sometimes I feel like the Scarecrow and sometime like the Tin Man, but never the Lion.
Thanks,
SM
February 14, 2018 at 12:01 am
SteveMalcolm - Tuesday, February 13, 2018 10:33 AMhttps://www.brentozar.com/pastetheplan/?id=H1rMn9evMThe second nested loop is warning that there is no join predicate. I'm still new to this so I'm confused. Is that because I am using a CTE to determine the values for two of the attributes? This presentation table is used in more that a few reports, and I don't want to create a second one for this very unique one.
Sometimes I feel like the Scarecrow and sometime like the Tin Man, but never the Lion.
Thanks,
SM
Can you post the DDL for the tables and the indices please?
😎
First thought would be to get rid of the Index Seek on the SLAnalysis table by adding a persisted calculated column instead of the LIKE, and an filtered index on that column, something like
COL_NAME AS (SIGN(CHARINDEX('SuperName','ACCUM',0))
the next would be to eliminate Hash Match which is doing the distinct on all the output columns from that table.
Then the Key Lookups from the SLAnalysisReportData table could probably be eliminated and the table scan of the FiscalPeriod table.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply