This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rawdata:environments [2011/04/04 19:39] deb |
integration:rawdata:environments [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| [[integration:rawdata:updates|Updates]] | | [[integration:rawdata:updates|Updates]] | | ||
| [[integration:rawdata:creation|Generating Data Files]] | | [[integration:rawdata:creation|Generating Data Files]] | | ||
| - | [[integration:rawdata:implementation|Implementation Guides]] | + | [[integration:rawdata:integration|Integration Guides]] |
| ---- | ---- | ||
| Line 20: | Line 20: | ||
| {{:integration:rawdata:basic_architecture_raw_data_files.png|}} | {{:integration:rawdata:basic_architecture_raw_data_files.png|}} | ||
| - | The instructions for referencing the raw data files in CREATE TABLE statements vary based on the file type. Consult the [[integration:rawdata:implementation|Implementation Guides]] for each type of raw data file for instructions on adding them to Omnidex Environment Files. | + | The instructions for referencing the raw data files in CREATE TABLE statements vary based on the file type. Consult the [[integration:rawdata:integration|Integration Guides]] for each type of raw data file for instructions on adding them to Omnidex Environment Files. |
| ==== 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. | ||