Hi all, I'm maintaining applications that access a SQL 2000 database that badly needs some tuning. I ran the Database Engine Tuning Advisor to see what recommendations it could make. On the table that I suspected was causing a lot of performance issues, it had recommended that about 70 different sets of statistics be added to one table. It also recommended more indexes, but that's another topic. There are currently about 12 sets of statistics currently on that table. While I do think that this table does need more indexes and statistics, 70 seem to me like that's too many. I don't know if I am going to be given the time to experiment with analyzing the queries and seeing which statistics make the most sense, and applying them one at a time. If I'm not given the time, and forced to just go with whatever the Database Engine Tuning Advisor, is this going to have a negative impact in other areas?