Composite Index Question

I have a rather large table that is queried in many different ways but
only has 6 fields. My question is: Is it better to have multiple
composite indexes that are tailered specifically to each of the queries
that are run? or is it better to have a few single column indexes?
I am using SQL SErver 2000.
Thanks in advance.
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!As always, it depends. I'd suggest putting together a test script of all of
the queries your table is going to get and run that script through the Index
Tuning Wizard. That will be a good first step toward getting your indexing
down. After that, I'd revisit your queries, to see if any rewrites will
coax a bit more speed.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
.
"Debbie" <anonymous@.email.com> wrote in message
news:%23QCUGHWWEHA.4048@.TK2MSFTNGP12.phx.gbl...
I have a rather large table that is queried in many different ways but
only has 6 fields. My question is: Is it better to have multiple
composite indexes that are tailered specifically to each of the queries
that are run? or is it better to have a few single column indexes?
I am using SQL SErver 2000.
Thanks in advance.
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!