This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:features:grids:creation [2012/04/04 15:55] doc |
admin:features:grids:creation [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 18: | Line 18: | ||
| Omnidex Grids are straightforward to administer. Each grid node is a separate Omnidex environment, with an environment file, indexes and data. For convenience, there are methods to share a single Omnidex environment file across multiple nodes. There are also methods to share data files across multiple nodes. | Omnidex Grids are straightforward to administer. Each grid node is a separate Omnidex environment, with an environment file, indexes and data. For convenience, there are methods to share a single Omnidex environment file across multiple nodes. There are also methods to share data files across multiple nodes. | ||
| - | |||
| - | Before creating an Omnidex Grid, you must first have a [[admin:features:grids:partitions | partitioning scheme]] and a [[admin:features:grids:distribution | distribution plan]]. These will be needed during the steps of creating an Omnidex Grid. | ||
| - | |||
| - | These instructions describe how to create an Omnidex Grid using SQL Statements. It is also possible to create an Omnidex Grid using the [[admin:features:grids:creation:odxadmin| Omnidex Administrator]]. | ||
| ==== Steps to create an Omnidex Grid using SQL Statements ==== | ==== Steps to create an Omnidex Grid using SQL Statements ==== | ||
| Line 70: | Line 66: | ||
| Here is an example of a CREATE ENVIRONMENT statement for an Omnidex Grid. | Here is an example of a CREATE ENVIRONMENT statement for an Omnidex Grid. | ||
| - | <code sql> | + | <code> |
| create environment "list_env" | create environment "list_env" | ||
| maxthreads 4 | maxthreads 4 | ||
| Line 99: | Line 95: | ||
| Here is an example of a CREATE DATABASE statement for an Omnidex Grid. | Here is an example of a CREATE DATABASE statement for an Omnidex Grid. | ||
| - | <code sql> | + | <code> |
| create database "list" | create database "list" | ||
| node NODE01 | node NODE01 | ||
| Line 133: | Line 129: | ||
| Here is an example of a CREATE TABLE statements for an Omnidex Grid. | Here is an example of a CREATE TABLE statements for an Omnidex Grid. | ||
| - | <code sql> | + | <code> |
| create table "HOUSEHOLDS" | create table "HOUSEHOLDS" | ||
| node NODE01 | node NODE01 | ||
| Line 163: | Line 159: | ||
| As discussed in the [[admin:features:grids:partitions#how_are_referential_constraints_handled_such_as_primary_and_foreign_keys| partition scheme]], it is necessary to partition tables so that referential integrity is maintained. Typically, the parent is partitioned using criteria, as shown for HOUSEHOLDS above, and the child is partitioned along the foreign key. The PARTITION BY clause for a child shows the join criteria, as shown below: | As discussed in the [[admin:features:grids:partitions#how_are_referential_constraints_handled_such_as_primary_and_foreign_keys| partition scheme]], it is necessary to partition tables so that referential integrity is maintained. Typically, the parent is partitioned using criteria, as shown for HOUSEHOLDS above, and the child is partitioned along the foreign key. The PARTITION BY clause for a child shows the join criteria, as shown below: | ||
| - | <code sql> | + | <code> |
| create table "INDIVIDUALS" | create table "INDIVIDUALS" | ||
| node NODE01 | node NODE01 | ||