ubject: RE: [GENERAL] estemated number of rows and optimiser effeciency
>> I am wondering, why the historical data (real result of the query) does
not affect the execution plan. For example, If I ran the query 10 times I
always get around 6500 instead of 5.5 million in the top most execut
>> I am wondering, why the historical data (real result of the query) does
not affect the execution plan. For example, If I ran the query 10 times I
always get around 6500 instead of 5.5 million in the top most execution plan
node.
The likely accurate, if cheeky, answer is simply that no one has
Hello,
I know that the optimizer, uses the number of rows to calculate the total
query execution time. In complex queries, it is very difficult to know the
number of rows in the expected result. This certainly affects the optimizer to
very great extent. I have a view and it should return aro
