This shows you the differences between two versions of the page.
|
admin:basics:overview:updates [2012/01/24 21:25] doc |
admin:basics:overview:updates [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ~~NOTOC~~ | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | |||
| - | ====== Administration ====== | ||
| - | |||
| - | ===== Introduction to Omnidex Fundamentals ===== | ||
| - | |||
| - | [[admin:basics:home | Environments ]] | | ||
| - | [[admin:basics:overview:sqlengine | SQL Engine]] | | ||
| - | **[[admin:basics:overview:updates | Updates]]** | | ||
| - | [[admin:basics:overview:network | Network Services]] | ||
| - | ---- | ||
| - | \\ | ||
| - | |||
| - | |||
| - | === Omnidex Updates === | ||
| - | |||
| - | Omnidex allows databases to be updated either in batch or online. The large majority of companies choose to update their databases in batch, and this is in keeping with the design of Omnidex and the nature of large databases. Databases with lots of data and lots of indexes are inherently difficult to update online. Relational databases that have just a few indexes per table are often updated online; however, this in itself can cause performance problems. Omnidex databases with hundreds of indexes are best updated in batch. | ||
| - | |||
| - | Omnidex provides high-speed, batch approaches to updating indexes that are must faster than relational databases, processing at rates of 1 billion index entries an hour. | ||
| - | |||
| - | [[admin:basics:updates:home | More >]] | ||
| - | |||
| - | ===== ===== | ||
| - | ---- | ||
| - | \\ | ||
| - | |||
| - | ** [[admin:basics:overview:sqlengine | Prev]] | [[admin:basics:overview:network | Next]] ** | ||
| - | |||
| - | ====== Additional Resources ====== | ||
| - | See also: | ||
| - | {{page>:admin:basics:see_also&nofooter&noeditbtn}} | ||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||