Hi,
We have been looking at doing some performance tuning on SQL Server and have had a play with the Tuning Engine in SQL Server 2005 in our test environment. We ran the trace for tuning and put the workload to the test and it suggested the creation of a load of new statistics and one or two keys, which the developers can now evaluate. We did have autstats on for the live environment and it seems to have created a load of statistics which may not be relevant at all. A few questions now which various bit of reference material (e.g. http://www.developer.com/db/article.php/3622881) have not been able to clear up, which hopefully one of the experts here can help with.
If we turn off autostats we will have a step in our maintenance plan to update statistics every night but…
Will we need to run the tuninig engine from time to time to identify stats that are missing, the maintenance plan seems to only update existing stats?
How do we get rid of rubbish stats that exist in our DB as a result of having had autostats on? DBCC SHOW_STATISTICS as a manual job on each table would take ages, does anybody have a script that identifies and removes useless stats or is it irrelevant anyway if autostats are off?
Regards
Meint