Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 28, 2004 12:17 PM
> To: Jeff Smelser
> Cc: [EMAIL PROTECTED]
> Subject: Re: increasing mysql/table performance..
>
>
> It is possible to have too many indexes. Usually you tune your
You are correct. It's not necessary to change your SQL statements to take
advantage of indices.
Redefining your tables may not be necessary, but I can see areas where you
might see benefits.
One example would be the stateVAL field in the first table. It looks like
you're storing an abbreviati
It is possible to have too many indexes. Usually you tune your indexes to
fit the majority of your queries. Definitely index the fields that are
used to JOIN your tables. Consider multi-column indexes more than lots of
single-column indexes as MySQL will use only one index per table for any
que
> Um.. Are you serious? thats all you do, create indexes?
Ok, I'm assuming familiarity with efficient schema design since joins are
being used. I'm excluding factors like system hardware, system load, OS,
MySQL performance tuning, etc..
And by efficient schema design, I'm referring to proper sep
| 1 | |
| 1 | SIMPLE | u1| eq_ref | PRIMARY | PRIMARY |
4 | colleges.p1.university_urlID | 1 | Using where |
++-----+---+----+------+-+--
---+--+---+
one suggestion would be to get the latest mysql performance tuning book
from o'reilly. its pretty good.
bruce wrote:
hi...
i've got a basic question (with probably many answers)
i'm creating a php/web app that uses mysql tbls. i have a number of pages
that do various selects using 'left joins'/'ri
On Tuesday 28 September 2004 01:02 pm, Ed Lazor wrote:
> I usually create an index for each criteria being checked against in the
> SQL statements.
>
> For example, for this query
>
> Select * from products where ProductID = 'aeg8557'
>
> I'd create an index on ProductID. The same thing applies if
I usually create an index for each criteria being checked against in the SQL
statements.
For example, for this query
Select * from products where ProductID = 'aeg8557'
I'd create an index on ProductID. The same thing applies if you're pulling
data from multiple tables.
For this query:
Selec
hi...
i've got a basic question (with probably many answers)
i'm creating a php/web app that uses mysql tbls. i have a number of pages
that do various selects using 'left joins'/'right joins'/etc...
i'm getting to the point where most of the basic logic works. now i want to
start figuring out ho
