This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
admin:indexing:creation:home [2012/01/30 16:36] doc |
admin:indexing:creation:home [2012/03/02 20:20] doc |
||
|---|---|---|---|
| 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]] | ||
| - | + | ---- | |
| - | ==== Overview ==== | + | === Overview === |
| Most relational databases, such as Oracle, SQL Server and MySQL, encourage administrators to create a few carefully-chosen indexes on a table. These indexes are created using the CREATE INDEX statement, which sequentially scans the table and populates the index. A table with three or four indexes will require three or four CREATE INDEX statements, each of which will sequentially scan the table and populate the index. | Most relational databases, such as Oracle, SQL Server and MySQL, encourage administrators to create a few carefully-chosen indexes on a table. These indexes are created using the CREATE INDEX statement, which sequentially scans the table and populates the index. A table with three or four indexes will require three or four CREATE INDEX statements, each of which will sequentially scan the table and populate the index. | ||