Easing Into Using the New AutoStats Feature - comment by nazygholizadeh

Hi Carrie,
Do we need to do some clean up before we start a new analyze job in stats manager.
I have been running Analyze jobs for differernt databases, and every time the job runs longer than before.
The last job I ran for our EMEA region databases using PDCRINFO for 3 weeks ran 2.5 days!
I see that we can set Viewpoint to cleanup the TDSTATS tables,, but the default is clea everythin that is 30 days old.  Would that help?  Is it the insert into this table that is the issue?
If yes, should we delete ALL rows (can we do it manually withouth harming anything), to make things faster?
 
I have an incident opened on this,, but have not heard for few days..  Wondering if you can tell me what causes the analyze job run so long.
 
We have PDCR setup.  Stats on those tables get collected, as set up by the PDCR process.
We have had USECOUNT loggingfor along time.
I also enabled XMLPLAN and STATSUSAGE on ALL in DBQL about 10 days ago..
Thanks,