Very strange execution plan estimated rows was really large
-
Just curios about following execution plan, one nested loop with two input (one estimated rows:3381 and another estimated rows:1) comes outs a estimation 27031900 rows, is it normal?
-
This was removed by the editor as SPAM
-
Without being able to see the rest of the execution plan nor have the execution plan where we can drill into the properties of each node, it's likely to remain a mystery. 😉
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) - DBA328 - Tuesday, December 11, 2018 2:23 AMJust curios about following execution plan, one nested loop with two input (one estimated rows:3381 and another estimated rows:1) comes outs a estimation 27031900 rows, is it normal?
Use this and share it
https://www.brentozar.com/pastetheplan/Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/ - DBA328 - Tuesday, December 11, 2018 2:23 AM
Post the execution plan please!
😎 - DBA328 - Tuesday, December 11, 2018 2:23 AMJust curios about following execution plan, one nested loop with two input (one estimated rows:3381 and another estimated rows:1) comes outs a estimation 27031900 rows, is it normal?
What do the statistics look like for the data involved?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore RooseveltAuthor of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply