I have a vary large table that runs slower than cold tar. Are indexes the way to go? It is mostly slow on pulling data. How often should I run them? Data is inserted into the table all the time (some have up to 100 rows added a day and others may have 1000 a day). Do I create indexes for all the fields I search from?

Chris

__________________
Chris

Indexes are the way to go because it only searches through 4 levels instead of the entire table. You want to add indexes to fields like phone numbers. You don't want to index a city unless there a a good number of cities ie. if everyone was from New York it would be pointless.

If I'm not mistaken, SQL Server will update the indexes automatically when records change.

Yes. You should create indices that match your table relationships and your look-up search criteria with an eye on not over-indexing. Your database may provide reports or indexing suggestions. Think also about clustering that physically arranges the records in the index order.

Andy

try to collect queries running on that table and use the index tuning tool to get you the best set for indicies..

Ahmed Ali
Software Developer