This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
integration:rawdata:environments [2011/03/14 14:21] 127.0.0.1 external edit |
integration:rawdata:environments [2011/04/04 19:45] deb |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| ==== Environments and Raw Data Files ==== | ==== Environments and Raw Data Files ==== | ||
| - | Omnidex provides access to raw data files by creating a database around them. The Omnidex administrator creates an Omnidex Environment File that declares a complete database with table and column definitions, table constraints and Omnidex indexes. The tables simply point to the raw data files as their source of data. Omnidex applications can then query the database without any concern whether the underlying data came from a relational database or raw data files. | + | Omnidex provides access to raw data files by creating a database around them. The Omnidex administrator creates an Omnidex Environment File that declares a complete database with table and column definitions, table constraints, and Omnidex indexes. The tables simply point to the raw data files as their source of data. Omnidex applications can then query the database without any concern whether the underlying data came from a relational database or raw data files. |
| {{:integration:rawdata:basic_architecture_raw_data_files.png|}} | {{:integration:rawdata:basic_architecture_raw_data_files.png|}} | ||
| 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. | ||