October 7, 2004 at 11:38 am
I have a SQL Server 7.0 database that I ran Profiler from my sql2000server desktop PC to grab 2 hours worth of data into a table in my sql2000server desktop.
I am now trying to use the Index Tuning Wizard to analyze this workload and check the original sql7.0 database indexes.
It's been running for hours and now doesn't appear to be doing anything....I'm not sure if it's hung or not.
It did create 2 temp files that haven't updated since the beginning.
Is there any problems with using the Index Wizrd on a 2000 machine against a 7.0 database perhaps?
Does anyone have any other ideas....or does it normally takes hours to go through?
October 8, 2004 at 4:02 am
it often sits there and doesnt look like it's doing very much.
Please dont rely entirely on the wizard for your indexing requirements, it often makes mistakes or fails entirely to pick up on a really beneficial index. It's not for nothing that it's being called the index tuning advisor in SQL 2005, too many people see the work wizard and expect it to come up with the best answers all the time.
A better way would be to use profiler to monitor on duration and then look at tuning the system for the queries that run for a long time. Once you're happy with that then look at tuning the queries that are ran lots and see if there are any ways of improving them (which will take a lot of the load off the server).
Using Profiler and query plans are way better than the ITW in my opinion but I suppose that you need to know what to tune first.
Mike
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply