This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:basics:updates:home [2011/04/12 15:12] doc |
admin:basics:updates:home [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| ===== Omnidex Updates ===== | ===== Omnidex Updates ===== | ||
| - | **[[admin:basics:updates:home|Overview]]** -> [[admin:basics:updates:periodic|Periodic Updates]] -> [[admin:basics:updates:online|Online Updates]] -> [[admin:basics:updates:triggers|Triggered 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]] | ||
| ---- | ---- | ||
| Line 15: | Line 18: | ||
| 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. | 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. | ||
| - | Omnidex specializes in very large databases that are heavily indexed. This combination is more and more common in the industry as companies require increasing intelligence gathered from larger and larger databases. The classic approach of inserting data into a database simply doesn't scale well. Most relational databases can support inserting hundreds of thousands of rows into a table, but not hundreds of millions. Once a database is heavily indexed, the classic approach of inserting data into a database falters even more. Most administrators would be understandably reluctant to insert hundreds of thousands of rows into a table with tens or hundreds of indexes. | + | Omnidex specializes in very large databases that are heavily indexed. This combination is more and more common in the industry as companies require increasing intelligence gathered from larger and larger databases. The classic approach of inserting data into a database simply doesn't scale well. Most relational databases can support inserting hundreds of thousands of rows into a table, but not hundreds of millions. If the database is heavily indexed, the classic approach of inserting data into a database falters even more. Most administrators would be understandably reluctant to insert hundreds of thousands of rows into a table with tens or hundreds of indexes. |
| - | This has led to new approaches to handling large volumes of data. Companies frequently process their data in larger batches, and Omnidex specializes in this very approach. In contrast to the relational database, Omnidex is designed to regenerate all of the indexes on a table at the same time at processing rates of 1 billion index entries an hour ((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.)) <sup>1<sup>. This allows on Companies can process large numbers of updates by reindexing the database, by adding a new node to an Omnidex Grid, or by | + | This has led to new approaches to handling large volumes of data. Companies frequently process their data in larger batches, and Omnidex specializes in this approach. In contrast to the relational database, Omnidex is designed to regenerate all of the indexes on a table with a single scan of the data, processing rates of 1 billion index entries an hour<sup>,,1,,</sup>. [[admin:features:grids:home|Omnidex Grids]] also allow new nodes to be created and indexed independently from the rest of the database, allowing an incremental approach to updating the database. While it is impractical to drop and recreate large indexes in a relational database, it is fast and easy to regenerate the indexes with Omnidex. |
| - | <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. | + | For applications that require online updates, Omnidex supports the INSERT, DELETE and UPDATE statements and will update most kinds of Omnidex indexes in real time. Omnidex also supports an approach that uses triggers on relational databases to automatically capture all updates. Online updates have some [[admin:basics:updates:online|important restrictions]] that must be considered, but they can provide important flexibility to application designers. |
| ==== ==== | ==== ==== | ||
| - | **[[admin:basics:updates:periodic|Next]]** | + | ---- |
| + | <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.,, | ||
| + | |||
| + | **[[admin:basics:updates:offline|Next]]** | ||
| ====== Additional Resources ====== | ====== Additional Resources ====== | ||