Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
integration:rdbms:odbc:environments [2011/04/07 00:18]
doc
integration:rdbms:odbc:environments [2016/06/28 22:38] (current)
Line 23: Line 23:
 The Omnidex Environment File contains metadata that describes the database and the Omnidex configuration. ​ This includes the following connection and schema information for the underlying database: The Omnidex Environment File contains metadata that describes the database and the Omnidex configuration. ​ This includes the following connection and schema information for the underlying database:
  
-  * ODBC system, user or file datasource+  * ODBC system, useror file datasource
   * ODBC user and password ​   * ODBC user and password ​
-  * ODBC schema information tables, columns and datatypes+  * ODBC schema information tables, columnsand datatypes
   * ODBC primary and foreign key constraints   * ODBC primary and foreign key constraints
   * ODBC native indexes   * ODBC native indexes
Line 31: Line 31:
 === Generating an Omnidex Environment File === === Generating an Omnidex Environment File ===
  
-Omnidex can automatically generate the CREATE ENVIRONMENT,​ CREATE DATABASE, CREATE TABLE and CREATE INDEX statements needed for an Omnidex Environment File.  The [[dev:​sql:​statements:​extract:​home|EXTRACT]] statement will connect to the underlying database using ODBC, query the database'​s schema information,​ and generate the appropriate statements. ​ The EXTRACT statement can be issued through OdxSQL, or through any ODBC or JDBC application.+Omnidex can automatically generate the CREATE ENVIRONMENT,​ CREATE DATABASE, CREATE TABLEand CREATE INDEX statements needed for an Omnidex Environment File.  The [[dev:​sql:​statements:​extract:​home|EXTRACT]] statement will connect to the underlying database using ODBC, query the database'​s schema information,​ and generate the appropriate statements. ​ The EXTRACT statement can be issued through OdxSQL, or through any ODBC or JDBC application.
  
 <​code>​ <​code>​
Line 56: Line 56:
 == PASSWORD == == PASSWORD ==
  
-The password to be used when accessing ODBC.  This password must correspond to the user referenced in the USER option. ​ This option is required unless a user and password ​is included in the datasource.+The password to be used when accessing ODBC.  This password must correspond to the user referenced in the USER option. ​ This option is required unless a user and password ​are included in the datasource.
  
 == DATABASE == == DATABASE ==
Line 68: Line 68:
 == INDEX_DIRECTORY == == INDEX_DIRECTORY ==
  
-The INDEX_DIRECTORY option declares the directory to contain the Omnidex indexes. ​ This is not an ODBC setting, but rather path designation where indexes should be built. ​ This directory can include either absolute or relative path designations. ​ If this option is omitted, then the indexes will be built in the same directory as the Omnidex Environment File.+The INDEX_DIRECTORY option declares the directory to contain the Omnidex indexes. ​ This is not an ODBC setting, but rather ​path designation where indexes should be built. ​ This directory can include either absolute or relative path designations. ​ If this option is omitted, then the indexes will be built in the same directory as the Omnidex Environment File.
  
 === Limitations of the Omnidex EXTRACT statement === === Limitations of the Omnidex EXTRACT statement ===
Line 79: Line 79:
 === Manually Creating an Omnidex Environment File === === Manually Creating an Omnidex Environment File ===
  
-An Omnidex Environment File can also be created by manually issuing CREATE ENVIRONMENT,​ CREATE DATABASE, CREATE TABLE and CREATE INDEX statements in OdxSQL or using ODBC or JDBC.  If these statements are written to a text batch file, then that file can be submitted to OdxSQL using the USE command.+An Omnidex Environment File can also be created by manually issuing CREATE ENVIRONMENT,​ CREATE DATABASE, CREATE TABLEand CREATE INDEX statements in OdxSQL or using ODBC or JDBC.  If these statements are written to a text batch file, then that file can be submitted to OdxSQL using the USE command.
  
  
 
Back to top
integration/rdbms/odbc/environments.1302135527.txt.gz ยท Last modified: 2016/06/28 22:38 (external edit)