This is an old revision of the document!
Overview | Types | Creating | Maintaining | Deploying
An Omnidex Environment is a term that describes all the aspects an Omnidex database. This includes:
Typically, an Omnidex Environment is a directory with subdirectories that contain all of these elements. This is often the most convenient approach since whole directories are easy to move and back up. In many cases, however, the database and indexes are large enough that they must span multiple disk drives or even machines. In that case, the Omnidex Environment refers to the entire collection, even though it is disbursed. A common directory structure for an Omnidex Environment is shown below, and presumes a database named “simple”.*
Directory | Description |
---|---|
/simple | Root directory containing Omnidex Environment File |
/simple/dat | Directory containing any data files, such as raw data files or delimited files |
/simple/idx | Directory containing Omnidex indexes |
/simple/sql | Directory containing SQL files used in this environment |
/simple/log | Directory containing log files generated in this environment |
————————- | ———————————————————————————- |
* Note that this directory structure is not required, and any structure may be used.
An Omnidex Environment File is an XML file that contains all of the metadata about the database and the Omnidex indexes. It is created interactively using the Omnidex Administrator, or using SQL statements such as CREATE ENVIRONMENT, CREATE DATABASE, CREATE TABLE and CREATE INDEX. The metadata contained in an Omnidex Environment File includes:
Omnidex Environment Files also serve an important role in connections. An Omnidex Connection String points to an Omnidex Environment File. This means that the Omnidex Environment File is the starting point for nearly every Omnidex operation.
See also: