Is my memory getting that bad or did something change in how sql monitor
reports actual rows and executions?
I have a plan_line_id that's an index range scan on a table with 680,000
rows reporting an "actual rows" value of 220,000,000 and an "Executions"
value of 6,861,000.
I aways though it was ("executions" x "actual rows") that got passed up to
the parent operation but that's not making sense at the moment.
Chris