No ... having too many indexes can actually lead to decreased selection
speed. This is because SQL generates an execution plan in which it examines
the available indexes and picks the one(s) it thinks is best.
The way to maximize selection speed for a single query is to create and test
individual indexes and benchmark them. Don't forget to try various composite
indexes ... wide index containing more than a single column which typically
mach your Where and Order By clauses.
Note, that the available indexes are used for all queries against the table.
So optimization for a specific query could decrease speed of other queries.
Also, SQL provides the Index Tuning Wizard which allows you to select and
create an optimal set of indexes.
Cheers,
Bill
In a message dated 7/25/01 8:14:24 AM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
> > Index the table to hell and back
>
> >>Indexing too many fields, or the wrong combinations, can actualy hurt
> >>performance.
> >>It's best to put a few benchmarks in place, and add a few indices at a
> time.
>
> True.....indexes improve speed of selects but slow down inserts,updates and
> deletes as the whole index needs to be rebuilt every time data is changed.
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
