This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
admin:features:home [2012/03/02 19:56] doc |
admin:features:home [2012/04/04 16:47] doc |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| - | **[[admin:features:home|Concepts]]** | | + | **[[admin:features:home|Overview]]** | |
| - | [[admin:indexing:overview:snapshots|Snapshots]] | | + | [[admin:features:overview:snapshots|Snapshots]] | |
| - | [[admin:indexing:overview:grids|Grids]] | | + | [[admin:features:overview:grids|Grids]] | |
| - | [[admin:indexing:overview:rollups|Rollups]] | | + | [[admin:features:overview:rollups|Rollups]] | |
| - | [[admin:indexing:overview:geosearch|Geographic Searches]] | | + | [[admin:features:overview:geosearch|Geographic Searches]] | |
| - | [[admin:indexing:overview:expressioncols|Expression Columns]] | | + | [[admin:features:overview:expressioncols|Expression Columns]] | |
| - | [[admin:indexing:overview:segments|Segments]] | | + | [[admin:features:overview:segments|Segments]] | |
| - | [[admin:indexing:overview:attach|Attaching Data]] | + | [[admin:features:overview:attach|Attaching Data]] |
| ---- | ---- | ||
| - | \\ | ||
| - | === Indexing Concepts === | + | === Overview === |
| - | Omnidex provides a wide variety of indexing capabilities. The simplest applications may simply require a few indexes to be added, but other applications may use many more indexing capabilities. It is useful to get a quick overview of the indexing capabilities of Omnidex. Customers commonly purchase Omnidex for its basic indexing capabilities, only to discover there is more more available. | + | 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. |
| - | Omnidex takes a completely different approach to indexing that other databases. Instead of adding a single index here and there, administrators are encouraged to index all of the columns used in criteria, table joins, aggregations, ordering, and in certain circumstances, even retrievals. Using this approach, most queries will be fulfilled through the indexes without having to access the database at all. | + | 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. |
| - | That being said, indexing is not the answer to every problem. There are times to use indexes and times to avoid them. | + | 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. |
| - | |< 80% 50% 50% >| | + | 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. |
| - | ^ Use Omnidex indexes for ... ^ Avoid Omnidex indexes for ... ^ | + | |
| - | | isolating a small number of rows | retrieving a large number of rows | | + | |
| - | | processing complex searches | single-use databases | | + | |
| - | | using more flexible search options | | | + | |
| - | | obtaining counts and aggregations | | | + | |
| - | | joining multiple tables | | | + | |
| - | | ordering a query result | | | + | |
| - | + | ||
| - | \\ | + | |
| - | it is useful to understand how Omnidex uses indexes to optimize each of these situations. This knowledge will help in choosing the best selection of Omnidex indexes and options. | + | 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:indexing:concepts:home | More >]] | ||
| ===== ===== | ===== ===== | ||
| ---- | ---- | ||
| \\ | \\ | ||
| - | **[[admin:indexing:overview:indexes|Next]]** | + | **[[admin:features:overview:snapshots|Next]]** |