Thanks for the tips. So it seems that:
1) I should index the most often used ones.
I am not sure what OLTP/OLAP means?
Peter
On 9/20/06, Peter Brawley [EMAIL PROTECTED] wrote:
Peter
It doesn't seem like it would make sense to make an index for every
possible combination... but there
Peter
I am not sure what OLTP/OLAP means?
T=transaction (processing is mostly inserts, updates),
A=Analysis(processing is mostly for reports), see
http://wiki/en/wikipedia.org/OLAP. You keep 2 versions of your data, one
optimised for inserts/updates, one optimised for reporting, you update
Hi,
I've been trying to figure this out for a while..
I have a table ITEMS with about 15 fields that can be used in any
combination in where queries, let me call these fields f1 to f15.
There are also 3 fields used for ordering, let's call them o1 to o3.
So the table is:
tablename (id, title,
-Original Message-
From: Peter Van Dijck [mailto:[EMAIL PROTECTED]
Sent: Thursday, 21 September 2006 3:14 p.m.
To: MYSQL General List
Subject: Question about LOTS of indexes on a table
Hi,
I've been trying to figure this out for a while..
I have a table ITEMS with about 15 fields that can be used
Peter
It doesn't seem like it would make sense to make an index for
every
possible combination... but there must be a way to do this
intelligently?
It does not make sense for inserts and updates, but it sure makes sense
for reproting, so have you considered separating your functionality
