This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
admin:indexing:strategies:criteria [2012/01/30 17:45] doc |
admin:indexing:strategies:criteria [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 24: | Line 24: | ||
| In the following statement, look for the columns used as criteria in the WHERE clause | In the following statement, look for the columns used as criteria in the WHERE clause | ||
| - | <code sql> | + | <code> |
| select HOUSEHOLD, ADDRESS, CITY, STATE, ZIP | select HOUSEHOLD, ADDRESS, CITY, STATE, ZIP | ||
| Line 39: | Line 39: | ||
| In this example, you might want to use QuickText indexes. QuickText indexes will parse and index each word in the column and will allow them to be searched case-insensitively. | In this example, you might want to use QuickText indexes. QuickText indexes will parse and index each word in the column and will allow them to be searched case-insensitively. | ||
| - | <code sql> | + | <code> |
| select INDIVIDUAL, NAME, PHONE | select INDIVIDUAL, NAME, PHONE | ||
| Line 53: | Line 53: | ||
| If a column has low cardinality, meaning that it has less than 32 distinct values, it should be indexed as an Omnidex Bitmap index. This improves performance and saves disk space. | If a column has low cardinality, meaning that it has less than 32 distinct values, it should be indexed as an Omnidex Bitmap index. This improves performance and saves disk space. | ||
| - | <code sql> | + | <code> |
| select INDIVIDUAL, NAME, PHONE | select INDIVIDUAL, NAME, PHONE | ||
| Line 67: | Line 67: | ||
| This sample environment file shows the Omnidex indexes that will optimize these queries. | This sample environment file shows the Omnidex indexes that will optimize these queries. | ||
| - | <code sql> | + | <code> |
| create environment | create environment | ||
| in "simple.xml" | in "simple.xml" | ||