This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:features:grids:distribution [2011/01/10 22:22] els |
admin:features:grids:distribution [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ~~NOTOC~~ | ||
| + | |||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| Line 5: | Line 7: | ||
| ===== Omnidex Grids ===== | ===== Omnidex Grids ===== | ||
| - | [[admin:features:grids:home|Overview]] -> [[admin:features:grids:partitions|Partitioning Scheme]] -> **[[admin:features:grids:distribution|Distribution Plan]]** -> [[admin:features:grids:creation|Grid Creation]] | + | [[admin:features:grids:home|Overview]] | [[admin:features:grids:partitions|Partitioning Scheme]] | **[[admin:features:grids:distribution|Distribution Plan]]** | [[admin:features:grids:creation|Grid Creation]] |
| ---- | ---- | ||
| Line 16: | Line 18: | ||
| Many Omnidex customers use [[admin:features:snapshots:home | Omnidex Snapshots]] for their grids. An Omnidex Snapshot is a physical copy of the underlying data stored in a choice of different portable file formats, such as fixed-length records or comma delimited records. The excellent performance and high portability of Omnidex Snapshots make them an ideal vehicle for distributing a database across a grid. | Many Omnidex customers use [[admin:features:snapshots:home | Omnidex Snapshots]] for their grids. An Omnidex Snapshot is a physical copy of the underlying data stored in a choice of different portable file formats, such as fixed-length records or comma delimited records. The excellent performance and high portability of Omnidex Snapshots make them an ideal vehicle for distributing a database across a grid. | ||
| - | Other customers logically partition their relational databases through the use of relational views. Each partition is supported by a relational view that narrows the table to specific rows based on the partition qualifier. These grids are usually maintained on a single server since it must retain tethered to the relational database. | + | Other customers logically partition their relational databases through the use of relational views. Each partition is supported by a relational view that narrows the table to specific rows based on the partition qualifier. These grids are usually maintained on a single server since it must remain tethered to the relational database. |
| === 2. Are there requirements for scalability, replication or redundancy? === | === 2. Are there requirements for scalability, replication or redundancy? === | ||