This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rawdata:creation [2011/04/04 21:33] deb |
integration:rawdata:creation [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: | ||
| ==== External Sources for Raw Data Files ==== | ==== External Sources for Raw Data Files ==== | ||
| - | Raw data files are commonly generated from relational databases, third party tools, vendor subscriptions and applications. | + | Raw data files are commonly generated from relational databases, third party tools, vendor subscriptions, and applications. |
| * **RDBMS Exports** - Relational databases and office products often have export utilities that create raw data files. These may be delimited files or fixed-length data files. | * **RDBMS Exports** - Relational databases and office products often have export utilities that create raw data files. These may be delimited files or fixed-length data files. | ||
| - | * **Third-party Tools** - Extract, transformation and loading (ETL) tools can produce a wide variety of delimited and fixed-length data file. | + | * **Third-party Tools** - Extract, transformation and loading (ETL) tools can produce a wide variety of delimited and fixed-length data files. |
| * **Vendor Subscriptions** - Vendors often distribute their data using delimited or fixed-length data files, either as one-time distributions or regular subscriptions. | * **Vendor Subscriptions** - Vendors often distribute their data using delimited or fixed-length data files, either as one-time distributions or regular subscriptions. | ||
| Line 34: | Line 34: | ||
| Omnidex SQL statements can be used to generate different types of raw data files. The [[dev:sql:statements:export|EXPORT]] statement can be used to convert the results of any SQL statement into raw data files supported by Omnidex. These EXPORT statements can be as simple as exporting all of the columns from a table, or as complex as joining multiple tables with complex aggregations and expressions. | Omnidex SQL statements can be used to generate different types of raw data files. The [[dev:sql:statements:export|EXPORT]] statement can be used to convert the results of any SQL statement into raw data files supported by Omnidex. These EXPORT statements can be as simple as exporting all of the columns from a table, or as complex as joining multiple tables with complex aggregations and expressions. | ||
| - | In the examples below, Omnidex EXPORT statements are used to create raw data files. These examples create fixed-length data files, but there are options to cause files to be created using different types. Consult the [[integration:rawdata:implementation|Implementation Guides]] to see instructions for exporting data to each type of file. | + | In the examples below, Omnidex EXPORT statements are used to create raw data files. These examples create fixed-length data files, but there are options to cause files to be created using different types. Consult the [[integration:rawdata:integration|Integration Guides]] to see instructions for exporting data to each type of file. |
| == Omnidex SQL Example 1: Export of a table == | == Omnidex SQL Example 1: Export of a table == | ||
| Line 88: | Line 88: | ||
| **[[integration:rawdata:updates|Prev]]** | | **[[integration:rawdata:updates|Prev]]** | | ||
| - | **[[integration:rawdata:implementation|Next]]** | + | **[[integration:rawdata:integration|Next]]** |
| ====== Additional Resources ====== | ====== Additional Resources ====== | ||