This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:basics:environments:types [2012/01/19 21:15] doc |
admin:basics:environments:types [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 26: | Line 26: | ||
| Omnidex Environments can be comprised of multiple databases. These databases can be of different types as well. For example, an environment can contain a database pointing to Oracle tables, and also contain a database pointing to raw data files or delimited files. All databases can have Omnidex indexes, and queries against this environment can reference tables from both databases. This capability is of great benefit to those who have transient log files or transaction files that they want to query in conjunction with a primary relational database. | Omnidex Environments can be comprised of multiple databases. These databases can be of different types as well. For example, an environment can contain a database pointing to Oracle tables, and also contain a database pointing to raw data files or delimited files. All databases can have Omnidex indexes, and queries against this environment can reference tables from both databases. This capability is of great benefit to those who have transient log files or transaction files that they want to query in conjunction with a primary relational database. | ||
| + | |||
| + | For applications that require accessing multiple sources of data, it is also possible to temporarily [[admin:features:attach:home|attach a database or table]] to the current environment. This is useful for incorporating tables with search criteria from customers, or incorporating the results of previous orders. | ||
| === Omnidex Grid Environments === | === Omnidex Grid Environments === | ||