This shows you the differences between two versions of the page.
|
admin:features:home [2012/03/02 20:48] doc |
admin:features:home [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ~~NOTOC~~ | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | |||
| - | ====== Administration ====== | ||
| - | |||
| - | ===== Introduction to Omnidex Features ===== | ||
| - | |||
| - | |||
| - | **[[admin:features:home|Concepts]]** | | ||
| - | [[admin:indexing:overview:snapshots|Snapshots]] | | ||
| - | [[admin:indexing:overview:grids|Grids]] | | ||
| - | [[admin:indexing:overview:rollups|Rollups]] | | ||
| - | [[admin:indexing:overview:geosearch|Geographic Searches]] | | ||
| - | [[admin:indexing:overview:expressioncols|Expression Columns]] | | ||
| - | [[admin:indexing:overview:segments|Segments]] | | ||
| - | [[admin:indexing:overview:attach|Attaching Data]] | ||
| - | |||
| - | ---- | ||
| - | |||
| - | === Overview === | ||
| - | |||
| - | Omnidex has many features beyond its indexing technology and its SQL Engine. Many Omnidex features are designed to make it easy to deploy powerful and flexible applications, whether they are being deployed on a relational database or in a NoSQL environment. | ||
| - | |||
| - | Many Omnidex applications are created as data warehouses or data mines. These can be quickly and easily created using Omnidex Snapshots, which are snapshots in time of an underlying database. Omnidex Snapshots can be easily deployed on separate servers, and can also be easily replicated for scalability. Further scalability can be achieved using Omnidex Grids. | ||
| - | |||
| - | Many Omnidex application have special needs. Applications that do extensive aggregations may benefit from Rollup Tables, which can pre-aggregate tables for higher performance. Omnidex provides an indexed, geographic search that allows applications do perform easy radius searches. Omnidex also allows columns to be declared that are the result of an expression, and allows these expression-based columns to be indexed for high-performance queries. | ||
| - | |||
| - | Omnidex also provides methods of dynamically incorporating data into an environment. Tables and databases can be attached to the current environment, allowing queries to span data from multiple applications and multiple database types. Files containing criteria values can be imported into Omnidex Segments and easily referenced in queries. Multi-step queries can also use Omnidex Segments to capture the results of one query and use it as criteria in a future query. | ||
| - | |||
| - | All of these features are designed to enhance performance of applications, and to make it easy to deploy applications quickly. Each feature coordinates with the Omnidex Indexes to achieve the best performance possible. | ||
| - | |||
| - | |||
| - | ===== ===== | ||
| - | ---- | ||
| - | \\ | ||
| - | **[[admin:features:overview:snapshots|Next]]** | ||
| - | |||
| - | |||
| - | ====== Additional Resources ====== | ||
| - | See also: | ||
| - | {{page>:admin:indexing:see_also&nofooter&noeditbtn}} | ||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||