This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:basics:environments:create [2011/01/24 15:32] els |
admin:basics:environments:create [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | ====== Administration: Omnidex Basics ====== | + | ====== Administration: Omnidex Fundamentals ====== |
| ===== Omnidex Environments ===== | ===== Omnidex Environments ===== | ||
| Line 19: | Line 19: | ||
| There are two methods to create Omnidex Environment Files. They can be created interactively using the [[programs:odxadmin:home|Omnidex Administrator]], or they can be created using SQL statements such as [[dev:sql:statements:create_environment:home|CREATE ENVIRONMENT]], [[dev:sql:statements:create_database:home|CREATE DATABASE]], [[dev:sql:statements:create_table:home|CREATE TABLE]] and [[dev:sql:statements:create_index:home|CREATE INDEX]]. Once created, a simple Omnidex Environment File will look like this: | There are two methods to create Omnidex Environment Files. They can be created interactively using the [[programs:odxadmin:home|Omnidex Administrator]], or they can be created using SQL statements such as [[dev:sql:statements:create_environment:home|CREATE ENVIRONMENT]], [[dev:sql:statements:create_database:home|CREATE DATABASE]], [[dev:sql:statements:create_table:home|CREATE TABLE]] and [[dev:sql:statements:create_index:home|CREATE INDEX]]. Once created, a simple Omnidex Environment File will look like this: | ||
| - | <code sql> | + | <code> |
| > create environment | > create environment | ||
| >> in "simple.xml" | >> in "simple.xml" | ||
| Line 27: | Line 27: | ||
| > | > | ||
| > create database "SIMPLE" | > create database "SIMPLE" | ||
| - | >> type FLATFILE | + | >> type FILE |
| >> index_directory "idx" | >> index_directory "idx" | ||
| >> in "simple.xml"; | >> in "simple.xml"; | ||
| Line 33: | Line 33: | ||
| > | > | ||
| > create table "HOUSEHOLDS" | > create table "HOUSEHOLDS" | ||
| - | >> physical "dat\households.dat" | + | >> physical "dat/households.dat" |
| >> ( | >> ( | ||
| >> "HOUSEHOLD" CHARACTER(12), | >> "HOUSEHOLD" CHARACTER(12), | ||
| Line 48: | Line 48: | ||
| > | > | ||
| > create table "INDIVIDUALS" | > create table "INDIVIDUALS" | ||
| - | >> physical "dat\individuals.dat" | + | >> physical "dat/individuals.dat" |
| >> ( | >> ( | ||
| >> "INDIVIDUAL" CHARACTER(12), | >> "INDIVIDUAL" CHARACTER(12), | ||
| Line 77: | Line 77: | ||
| > | > | ||
| > create database "SIMPLE" | > create database "SIMPLE" | ||
| - | >> type FLATFILE | + | >> type FILE |
| >> index_directory "idx" | >> index_directory "idx" | ||
| >> in "simple.xml"; | >> in "simple.xml"; | ||
| Line 84: | Line 84: | ||
| > | > | ||
| > create table "HOUSEHOLDS" | > create table "HOUSEHOLDS" | ||
| - | >> physical "dat\households.dat" | + | >> physical "dat/households.dat" |
| >> ( | >> ( | ||
| >> "HOUSEHOLD" CHARACTER(12) omnidex, | >> "HOUSEHOLD" CHARACTER(12) omnidex, | ||
| Line 99: | Line 99: | ||
| > | > | ||
| > create table "INDIVIDUALS" | > create table "INDIVIDUALS" | ||
| - | >> physical "dat\individuals.dat" | + | >> physical "dat/individuals.dat" |
| >> ( | >> ( | ||
| >> "INDIVIDUAL" CHARACTER(12) omnidex, | >> "INDIVIDUAL" CHARACTER(12) omnidex, | ||
| Line 117: | Line 117: | ||
| ==== Updating Omnidex Indexes ==== | ==== Updating Omnidex Indexes ==== | ||
| - | When Omnidex indexing is added to an Omnidex Environment, only the metadata about each index is added to the environment. The indexes themselves are not built until an "UPDATE INDEXES" command is issued. This is of great benefit since it allows multiple indexes to be built with one scan of the data. Omnidex applications frequently involve many Omnidex indexes, and building them individually would be prohibitively slow. The example below connects to the newly create environment and updates the indexes. | + | When Omnidex indexing is added to an Omnidex Environment, only the metadata about each index is added to the environment. The indexes themselves are not built until an UPDATE INDEXES statement is issued. This is of great benefit since it allows multiple indexes to be built with one scan of the data. Omnidex applications frequently involve many Omnidex indexes, and building them individually would be prohibitively slow. The example below connects to the newly create environment and updates the indexes. |
| <code> | <code> | ||
| Line 124: | Line 124: | ||
| > | > | ||
| > update indexes | > update indexes | ||
| - | Updated indexes for HOUSEHOLDS | + | Database |
| - | Updated indexes for INDIVIDUALS | + | Table Rows CPU Elapsed |
| - | Omnidex indexes updated for environment USER_ENVIRONMENT | + | ---------------------------------------------------------------------------- |
| + | SIMPLE | ||
| + | HOUSEHOLDS 1,909 0:00 0:00 | ||
| + | INDIVIDUALS 5,000 0:00 0:00 | ||
| + | ---------------------------------------------------------------------------- | ||
| + | Total 0:00 0:03 | ||
| + | |||
| + | Omnidex indexes updated | ||
| + | > | ||
| </code> | </code> | ||