Easing Into Using the New AutoStats Feature - comment by carrie

Sandeep,
There are several good reasons to set NoDot0Backdown = TRUE when you get onto 14.10.  Use of extended object names require it, as does use of increased data block and spool block sizes.   You need that setting at TRUE in order to get the advantages of the new statistics histogram Version 6, which is able to record the Update/Delete/Insert counts at the time the stats were collected.   UDI counts are part of what UseCount logging creates, and without UDI counts being integrated in the stats collection process you will risk having a negative impact on the threshold Change Percent capability.  
 
If you want to use new 14.10 features fully, it's a good idea to set NoDot0Backdown = TRUE.
 
The only potential down side of this is that you will not be able to back down to 14.0, should you wish to do that.
 
In terms of the impact on AutoStats, the identification and deactivation of unused stats by Analyze jobs will still work even if NoDot0Backdown is False.  In that scenario, the Analyze job will still read the USECOUNT data that tracks optimizer stats usage.  However, as mentioned above, there will be negative impacts to other features, mostly the change-based THRESHOLD capabilties.
 
Although it is not the best practice, AutoStats does allow the automation of databases that do not have USECOUNT enabled.  Functionally, Analyze and Collect jobs should still run without failure but those features requiring UDI counts will not operate effectively.
 
Thanks, -Carrie