I am trying to understand the effect that forcing the update of statistics with a fullscan has on execution plan estimates.
As you can see it is off by 5 rows.
I then run:
UPDATE STATISTICS Person.Address WITH FULLSCAN UPDATE STATISTICS Person.Address [PK_Address_AddressID] WITH FULLSCAN GO EXEC sp_recompile 'Person.Address'; GO SELECT * FROM Person.Address OPTION(RECOMPILE)
However, it is still off by 5 rows. Why?
I know I shouldn't worry unless there is a performance problem. However, I am trying to understand the actual effect of a complete statistics update