This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
integration:rawdata:environments [2011/04/04 19:39] deb |
integration:rawdata:environments [2011/04/04 19:45] deb |
||
|---|---|---|---|
| Line 24: | Line 24: | ||
| ==== Combining Raw Data Files and Relational Databases ==== | ==== Combining Raw Data Files and Relational Databases ==== | ||
| - | Raw data files often supplement a relational database. For example, a transaction log or a supplemental data file may contain information that is ideal to correlate with a relational database. Companies that have been importing that data into the relational database can avoid that extra work, and use Omnidex to join those two data sources together instead. | + | Raw data files often supplement a relational database. For example, a transaction log or a supplemental data file may contain information that is ideal to correlate with a relational database. Companies importing that data into the relational database can avoid the extra work, and use Omnidex to join those two data sources together instead. |
| An Omnidex Environment File can include more than one database, and each database can be of a different type. An Omnidex Environment File can have one database that points to the underlying relational database, and a second database that points to a series of raw data files. When connected to this Omnidex Environment File, applications can issue SQL statements that join tables from both databases. | An Omnidex Environment File can include more than one database, and each database can be of a different type. An Omnidex Environment File can have one database that points to the underlying relational database, and a second database that points to a series of raw data files. When connected to this Omnidex Environment File, applications can issue SQL statements that join tables from both databases. | ||