As far as I know, Stats will give the cardinality info which will let the optimizer to know the estimated number of rows in the result which helps the optimizer to choose a good execution plan.. So, if the stats are not up to date, then the optimizer might think the estimated row is very small (say 10) and it might give you an execution plan which might take a longer time to execute (in case if your queries have lot of joins and stuff, then the optimizer will create a execution plan with lot of nested loop by considering it's gonna do this just for 10 rows etc..), , if you have updated the stats, the optimizer get to know the correct estimated number of rows (say 100 thousand) and prepare a different execution plans or it will give you a suggestion to create a missing index. Correct me if i'm wrong.. Hope this helps
What should be the average frequency to update stats incase the data is frequently changing or the data is frequently queried?
Thanks so much for sharing this
thank you so much for shared this GK.
Excellent
what really happens when update statistics
As far as I know, Stats will give the cardinality info which will let the optimizer to know the estimated number of rows in the result which helps the optimizer to choose a good execution plan..
So, if the stats are not up to date, then the optimizer might think the estimated row is very small (say 10) and it might give you an execution plan which might take a longer time to execute (in case if your queries have lot of joins and stuff, then the optimizer will create a execution plan with lot of nested loop by considering it's gonna do this just for 10 rows etc..), , if you have updated the stats, the optimizer get to know the correct estimated number of rows (say 100 thousand) and prepare a different execution plans or it will give you a suggestion to create a missing index.
Correct me if i'm wrong..
Hope this helps
SQL SERVER FILLS another tables with info about other tables
Thanks sir
sure. thank you