This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
integration:rdbms:home [2011/03/14 14:39] 127.0.0.1 external edit |
integration:rdbms:home [2011/03/31 16:02] deb |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ====== Integration: Relational Databases ====== | ====== Integration: Relational Databases ====== | ||
| - | **[[integration:rawdata:home|Overview]]** | | + | **[[integration:rdbms:home|Overview]]** | |
| - | [[integration:rawdata:types|File Types]] | | + | [[integration:rdbms:servers|Servers]] | |
| - | [[integration:rawdata:environments|Environments]] | | + | [[integration:rdbms:environments|Environments]] | |
| - | [[integration:rawdata:queries|Queries]] | | + | [[integration:rdbms:queries|Queries]] | |
| - | [[integration:rawdata:updates|Updates]] | | + | [[integration:rdbms:updates|Updates]] | |
| - | [[integration:rawdata:creation|Generating Data Files]] | | + | [[integration:rdbms:implementation|Implementation Guides]] |
| - | [[integration:rawdata:implementation|Implementation Guides]] | + | |
| ---- | ---- | ||
| ==== Overview ==== | ==== Overview ==== | ||
| - | Omnidex is frequently used to allow high-performance searches against raw data files. Sometimes, the raw data files come from an [[admin:features:snapshots:home|Omnidex Snapshot]], which is an extracted copy of data from an underlying relational database. Other times, the raw data files are received from vendors such as credit services and list providers. Other times, the data is the output of an internal application, such as a log file or transaction file. Regardless of the source of the data, Omnidex will allow raw data files to be treated as a table within a database. | ||
| - | Omnidex and raw data files are a well-tested and mature implementation of a NoSQL 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. Raw data files are a classic implementation of this principle. Omnidex can index raw data files of enormous size and allow high-performance searches without the limitations of a relational database. | + | 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. |
| - | Using Omnidex on raw data files has many advantages: | + | One of the first decisions for the administrator is which tables Omnidex should access. Omnidex applications often have tens or hundreds of indexes per table, delivering extremely high performance. The overhead for real-time updates on hundreds of indexes can be substantial, and as such, Omnidex is not a good solution for indexing a high-OLTP system. If applications are going to heavily index the data, Omnidex should be pointed to separate tables that are periodically refreshed. If the data is not heavily updated or if the Omnidex indexing is minimal, then real-time updates remain an option. |
| - | * **Access the rest of your data** - Most businesses miss out on the data that is stored outside their relational database. They simply don't have a way to search it. Omnidex turns raw data files into instant databases. | + | Omnidex is most commonly installed on read-only tables that are periodically refreshed. Some companies discover that Omnidex can also provide a complete SQL engine against [[integration:rawdata:home|raw data files]]. This introduces the possibility of creating low-cost, high-performance, autonomous query environments using data extracted from the relational database. These can be placed on a separate server, alleviating the load on the relational database while improving performance and increasing scalability. This can also lower licensing costs for the overall application. |
| - | + | ||
| - | * **No need for data imports** - Omnidex directly searches raw data files, flat files and delimited files without having to import them into a relational database. Ease the load on your servers and search the raw data files directly. | + | |
| - | + | ||
| - | * **Deploy your data while it is fresh** - Pushing raw data files through a relational database means you have to wait to deploy it. Index it directly and make it available while it is still fresh. | + | |
| - | + | ||
| - | * **Better Performance** - Omnidex usually performs better on raw data files than on relational databases. In general, Omnidex scans raw data files about three times faster than relational tables, given their simple structure and lower overhead. | + | |
| - | + | ||
| - | * **Built-in portability** - A database consisting of raw data files and Omnidex indexes can be easily copied to other servers. Simply copy a directory of files to wherever you want. | + | |
| - | + | ||
| - | * **Save license fees** - Save some money. The license fees for relational databases are not required on servers that simply host raw data files and Omnidex indexes. | + | |
| - | + | ||
| - | Omnidex can index and search raw data files using SQL statements, available through standard interfaces like ODBC and JDBC. Applications usually do not know that they are even accessing raw data files, except for an increase in performance. For many applications, the possible advantages of a relational databases are overwhelmed by the benefits of raw data files. | + | |
| ===== ===== | ===== ===== | ||
| - | **[[integration:rawdata:types|Next]]** | + | **[[integration:rdbms:servers|Next]]** |
| ====== Additional Resources ====== | ====== Additional Resources ====== | ||
| Line 45: | Line 31: | ||
| See also: | See also: | ||
| - | {{page>:integration:rawdata:see_also&nofooter&noeditbtn}} | + | {{page>:integration:rdbms:see_also&nofooter&noeditbtn}} |
| {{page>:bottom_add&nofooter&noeditbtn}} | {{page>:bottom_add&nofooter&noeditbtn}} | ||