This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:indexing:creation:declaring [2012/01/26 16:27] doc |
admin:indexing:creation:declaring [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ====== Administration: Omnidex Indexing ====== | ====== Administration: Omnidex Indexing ====== | ||
| - | ===== Indexing Creation ===== | + | ===== Index Creation ===== |
| [[admin:indexing:creation:home|Overview]] | | [[admin:indexing:creation:home|Overview]] | | ||
| Line 10: | Line 10: | ||
| [[admin:indexing:creation:updating|Updating Indexes]] | | [[admin:indexing:creation:updating|Updating Indexes]] | | ||
| [[admin:indexing:creation:files|Index Files]] | | [[admin:indexing:creation:files|Index Files]] | | ||
| - | [[admin:indexing:creation:updating|Maintenance]] | + | [[admin:indexing:creation:performance|Performance]] |
| + | ---- | ||
| ==== Declaring Indexes ==== | ==== Declaring Indexes ==== | ||
| Line 17: | Line 17: | ||
| - | <code sql> | + | <code> |
| > create table "HOUSEHOLDS" | > create table "HOUSEHOLDS" | ||
| >> physical "dat/households.dat" | >> physical "dat/households.dat" | ||
| Line 36: | Line 36: | ||
| Some indexes require more options or more information. For example, a multi-column index - an index containing more than one column - cannot be created by simply putting a keyword next to a column. These indexes can be created one of two ways. The first, and most common way, is to declare them in the CREATE TABLE statement following all of the constraint declarations as shown in the example below. | Some indexes require more options or more information. For example, a multi-column index - an index containing more than one column - cannot be created by simply putting a keyword next to a column. These indexes can be created one of two ways. The first, and most common way, is to declare them in the CREATE TABLE statement following all of the constraint declarations as shown in the example below. | ||
| - | <code sql> | + | <code> |
| > create table "HOUSEHOLDS" | > create table "HOUSEHOLDS" | ||
| >> physical "dat/households.dat" | >> physical "dat/households.dat" | ||
| Line 56: | Line 56: | ||
| Omnidex indexes can also be created using CREATE INDEX statement. This is a more traditional approach; however, most administrators prefer to use the CREATE TABLE statement since it is easier to differentiate which columns are indexed and which are not. In either case, these statements only declare the indexes, but do not populate the indexes. | Omnidex indexes can also be created using CREATE INDEX statement. This is a more traditional approach; however, most administrators prefer to use the CREATE TABLE statement since it is easier to differentiate which columns are indexed and which are not. In either case, these statements only declare the indexes, but do not populate the indexes. | ||
| - | <code sql> | + | <code> |
| > create omnidex index "STATE_CITY_ZIP" | > create omnidex index "STATE_CITY_ZIP" | ||
| >> on "HOUSEHOLDS" | >> on "HOUSEHOLDS" | ||
| Line 69: | Line 69: | ||
| </code> | </code> | ||
| - | Most commonly, administrators have an [[admin:basics:environments:home|Omnidex Environment File]] that contains all CREATE TABLE and CREATE INDEXES for their database. This SQL file can then be run using OdxSQL, regenerating the Environment File. Once the revised indexing has been declared, the indexes can be [[admin:indexing:creation:updating|updated]]. | ||
| ==== ==== | ==== ==== | ||