This shows you the differences between two versions of the page.
| Next revision Both sides next revision | |||
|
admin:features:attach:databases [2012/02/29 21:48] doc created |
admin:features:attach:databases [2012/02/29 22:54] doc |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| ==== Attaching Databases ==== | ==== Attaching Databases ==== | ||
| + | Omnidex allows entire databases to be attached to the current Omnidex Environment, incorporating all of their tables and Omnidex indexes. This can greatly expand the data available to query, and enhance the ability to optimize queries across multiple databases within the enterprise. Any type of database from any Omnidex Environment can be attached. This allows great flexibility in linking multiple applications together, such as linking a SQL Server customer database with a Raw Data File data warehouse. | ||
| + | Attaching databases can also be useful for applications that reference the results from previous queries in future queries. If the result set consists of a single column, such as a primary key, this can be done simply using [[admin:features:segments:home|Omnidex Segments]]; however, some applications identify the results of a previous query using multiple columns, or even multiple tables. Omnidex allows these results to be rendered into a miniature Omnidex database, complete with Omnidex indexing. Future queries can attach as many result set databases as needed to perform order suppression or other tasks, all taking advantage of the Omnidex indexes. | ||
| + | |||
| + | Attaching a database is simple, and uses the ATTACH DATABASE statement, as shown below: | ||
| + | |||
| + | <code> | ||
| + | attach database GEO | ||
| + | from geo.xml; | ||
| + | </code> | ||
| ==== ==== | ==== ==== | ||
| Line 24: | Line 33: | ||
| ====== Additional Resources ====== | ====== Additional Resources ====== | ||
| - | |||
| See also: | See also: | ||