This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:indexing:creation:files [2012/01/26 17:17] 127.0.0.1 external edit |
admin:indexing:creation:files [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 11: | Line 11: | ||
| **[[admin:indexing:creation:files|Index Files]]** | | **[[admin:indexing:creation:files|Index Files]]** | | ||
| [[admin:indexing:creation:performance|Performance]] | [[admin:indexing:creation:performance|Performance]] | ||
| + | ---- | ||
| ==== Index Files ==== | ==== Index Files ==== | ||
| - | Omnidex stores its indexes in files that are located in the Index Directory, which is specified in the CREATE DATABASE statement. The index files will all begin with the name of the database as declared in the CREATE DATABASE statement and will be followed by various names or numbers. Small databases will have only a handful of index files, while large databases may have hundreds of files. | + | Omnidex stores its indexes in files that are located in the Index Directory, which is specified in the [[dev:sql:statements:create_database:home|CREATE DATABASE]] statement. The index files will all begin with the name of the database as declared in the CREATE DATABASE statement and will be followed by various names or numbers. Small databases will have only a handful of index files, while large databases may have hundreds of files. |
| Line 35: | Line 35: | ||
| </code> | </code> | ||
| - | Omnidex indexes use an efficient index compression algorithm to reduce the physical footprint of Omnidex on the disk drive. In most cases, Omnidex requires about 2.5 bytes per keyword for its indexes. A keyword is an individual index entry. For standard Omnidex indexes, a keyword is an index value; for QuickText indexes, a keyword is a parsed word from the text field. Not that Omnidex Bitmap indexes require substantially less space, and FullText indexes require more space. | + | === Index File Compression === |
| + | |||
| + | Omnidex indexes use an efficient index compression algorithm to reduce the physical footprint of Omnidex on the disk drive. In most cases, Omnidex requires about 2.5 bytes per keyword for its indexes. A keyword is an individual index entry. For standard Omnidex indexes, a keyword is an index value; for QuickText indexes, a keyword is a parsed word from the text field. Note that Omnidex Bitmap indexes require substantially less space, and FullText indexes require more space. | ||
| ==== ==== | ==== ==== | ||