vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| - is it an OLTP or DSS environment ? - have you considered the option of not creating an index ?, but fragment the table on a column that is used in the query, this will force the optimizer to do fragment elimination (this way, there will be no overhead of maintaining the index ). -----Original Message----- From: owner-informix-list@iiug.org [mailto Sent: Tuesday, May 17, 2005 9:17 AM To: informix-list@iiug.org Subject: Index question We have a new query, with a where-clause: where a < b (a & b are date fields) and c = 0 (c can have values from 0 to 270) and d = "2" (d can have 4 different values) What is the best way to write this where clause, and which are the best indexes to use ? The table has a total of 32 million records. My own thoughts were: where d = "2" (get rid of most of the records) and c = 0 (reduce the above subset to about 25%) and a < b (leave the sequential scan for this remaining data set) And create indexes on c & d (which brings up another question - composite or stand alone ?) sending to informix-list sending to informix-list |