This shows you the differences between two versions of the page.
|
integration:rdbms:home [2011/03/14 16:29] els |
integration:rdbms:home [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ~~NOTOC~~ | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | |||
| - | ====== Integration: Relational Databases ====== | ||
| - | |||
| - | **[[integration:rawdata:home|Overview]]** | | ||
| - | [[integration:rawdata:servers|Servers]] | | ||
| - | [[integration:rawdata:environments|Environments]] | | ||
| - | [[integration:rawdata:queries|Queries]] | | ||
| - | [[integration:rawdata:updates|Updates]] | | ||
| - | [[integration:rawdata:implementation|Implementation Guides]] | ||
| - | |||
| - | ---- | ||
| - | ==== Overview ==== | ||
| - | |||
| - | Omnidex is often used to increase performance and improve flexibility on relational databases. Most companies that have invested in a relational database solution will continue to use the relational database as their core data store, but they may want to improve query performance or enhance their searches with [[admin:indexing:activecounts:home|ActiveCounts]], [[admin:indexing:powersearch:home|PowerSearch]] or [[admin:indexing:autocomplete:home|AutoComplete]]. Omnidex can access the data in the relational database and provide a high-speed query environment. | ||
| - | |||
| - | Omnidex applications often have tens to hundreds of indexes per table, delivering extremely high performance. As such, Omnidex is usually installed on read-only tables that are updated at periodic intervals. Omnidex does support online indexing; however, this is not suitable for high-volume OLTP applications. | ||
| - | |||
| - | Some companies that use relational databases discover that Omnidex can also provide a complete SQL engine against [[integration:rawdata:home|raw data files]]. This introduces the possibility of creating an low-cost, high-performance, autonomous query environment used data extracted from the relational database on a separate server. This can alleviate the load on the relational database while improving performance and increasing scalability. This can also lower licensing costs for the overall application. | ||
| - | |||
| - | |||
| - | ===== ===== | ||
| - | |||
| - | **[[integration:rawdata:types|Next]]** | ||
| - | |||
| - | ====== Additional Resources ====== | ||
| - | |||
| - | See also: | ||
| - | |||
| - | {{page>:integration:rawdata:see_also&nofooter&noeditbtn}} | ||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||