I think it will, Larry. It won't hurt to try anyway, as you can always drop
the index. The reason that I'm a little unsure is because I've not indexed
a date field before. I have also a 3-field (all numerics) concatenated
primary key on one large table (~300K records) and it ran like a dog without
indexes. I quickly added 6 indexes and it goes like a dream (6 being, 1 for
each field, 1 for the first 2 of 3 fields (a common query), another for the
1st and 3rd of the 3 (another very common join) and 1 for all 3. - I don't
have 2nd and 3rd as it's not a valid (for business reasons) join. Also, I
should have more indexes being for the 2nd and 1st, and for 3rd and 1st
(note the order) - but I'm careful I get the joins right (I check using
explain table).
--
David McRae dmcrae_at_dynamite.com.au
Canberra 02 6239 4247
Larry Schenavar wrote in message <6id85d$5l0$1_at_news1.infoave.net>...
>I have a 4 column table with 8 million rows. The key is 3 of the
>columns(one of them is a date). The table is very slow to query. Will
>creating an index on those three columns help? any other thoughts.
>
>
>--
>==============================
>Larry Schenavar
>Infrastructure Specialist /DB
>Electronic Data Systems, Inc
>
>Email: schenavar_at_northstate.net
>==============================
>
>
Received on Wed May 06 1998 - 17:01:15 CDT
