This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:features:snapshots:benefits [2012/03/30 21:11] doc |
admin:features:snapshots:benefits [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 48: | Line 48: | ||
| Omnidex Snapshots are ideal when paired with a underlying relational database. The underlying database can provide the transactional integrity needed for an OLTP application, while the Omnidex Snapshot can provide the flexibility and speed needed for an OLAP application. | Omnidex Snapshots are ideal when paired with a underlying relational database. The underlying database can provide the transactional integrity needed for an OLTP application, while the Omnidex Snapshot can provide the flexibility and speed needed for an OLAP application. | ||
| - | === The Power of Simple === | + | === The Power of Simplicity === |
| Omnidex Snapshots gain much of their power from their simplicity. Since an Omnidex Snapshot is simply a set of data and index files, they become easily managed and manipulated, avoiding the overhead of cost inserts or deletes from the relational databases. In this case, the simple solution is also the highest performing solution, since raw data files are extremely fast to process. | Omnidex Snapshots gain much of their power from their simplicity. Since an Omnidex Snapshot is simply a set of data and index files, they become easily managed and manipulated, avoiding the overhead of cost inserts or deletes from the relational databases. In this case, the simple solution is also the highest performing solution, since raw data files are extremely fast to process. | ||