This shows you the differences between two versions of the page.
|
admin:basics:updates:online [2011/04/12 16:59] doc |
admin:basics:updates:online [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ~~NOTOC~~ | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | |||
| - | ====== Administration: Omnidex Fundamentals ====== | ||
| - | |||
| - | ===== Omnidex Updates ===== | ||
| - | |||
| - | [[admin:basics:updates:home|Overview]] | | ||
| - | [[admin:basics:updates:offline|Offline Updates]] | | ||
| - | **[[admin:basics:updates:online|Online Updates]]** | | ||
| - | [[admin:basics:updates:grid|Grid Updates]] | | ||
| - | [[admin:basics:updates:triggers|Triggered Updates]] | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Online Updates ==== | ||
| - | |||
| - | Some applications require that databases are updated online. Omnidex supports online updates using the INSERT, DELETE and UPDATE statement, though there are restrictions that should be considered by the administrator and the application designer. When Omnidex processes an INSERT, DELETE or UPDATE statement, it updates the indexes for all affected columns before the operation is completed. Omnidex supports online updates on both relational databases and raw data files. | ||
| - | |||
| - | Omnidex processes online updates at a rate of approximately 2.5 million index entries an hour per table<sup>,,1,,</sup>. This means that rows can be inserted into a table with 25 indexes at a rate of approximately 100,000 per hour. For heavily indexed tables or larger numbers of updates, administrators should consider [[admin:basics:updates:offline|Offline Updates]] which process index updates at a rate that is 200 times faster. | ||
| - | |||
| - | Omnidex has many features that are designed for read-only databases. This is in keeping with Omnidex's design as a "NoSQL" database that favors performance on large database. The NoSQL movement is a loose term describing databases that search data outside of the traditional relational database. NoSQL databases are designed to improve performance by not adhering to the ACID requirements for databases governing **A**tomicity, **C**onsistency, **I**solation and **D**urability. | ||
| - | |||
| - | When choosing whether to use online updates, the following restrictions should be considered: | ||
| - | |||
| - | {{page>:admin:basics:updates:restrictions_insert&nofooter&noeditbtn}} | ||
| - | |||
| - | |||
| - | ==== ==== | ||
| - | |||
| - | ---- | ||
| - | <sup>,,1,,</sup> ,,An "index entry" represents an indexed column in a single row. If the column contains textual data that is indexed with QuickText or FullText indexes, then an "index entry"" represents a single word or number in an indexed column in a single row. Indexing rates are affected by machine performance, database performance, indexing options and concurrency.,, | ||
| - | |||
| - | **[[admin:basics:updates:batch|Next]]** | ||
| - | |||
| - | ====== Additional Resources ====== | ||
| - | See also: | ||
| - | {{page>:admin:basics:see_also&nofooter&noeditbtn}} | ||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||