This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rdbms:sqlserver:environments [2011/04/07 22:06] doc |
integration:rdbms:sqlserver:environments [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 23: | Line 23: | ||
| The Omnidex Environment File contains metadata that describes the SQL Server database and the Omnidex configuration. This includes the following connection and schema information: | The Omnidex Environment File contains metadata that describes the SQL Server database and the Omnidex configuration. This includes the following connection and schema information: | ||
| - | * SQL Server system, user or file datasource | + | * SQL Server system, user, or file datasource |
| * SQL Server user and password | * SQL Server user and password | ||
| - | * SQL Server schema information tables, columns and datatypes | + | * SQL Server schema information tables, columns, and datatypes |
| * SQL Server primary and foreign key constraints | * SQL Server primary and foreign key constraints | ||
| * SQL Server native indexes | * SQL Server native indexes | ||
| Line 31: | Line 31: | ||
| === Automatically Generating an Omnidex Environment File === | === Automatically 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 is used to connect to the SQL Server database, query the underlying schema information, and generate the appropriate statements. This statement can be issued through OdxSQL, or through any ODBC or JDBC application. | + | 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 is used to connect to the SQL Server database, query the underlying schema information, and generate the appropriate statements. This statement can be issued through OdxSQL, or through any ODBC or JDBC application. |
| <code> | <code> | ||
| Line 69: | Line 69: | ||
| == INDEX_DIRECTORY == | == INDEX_DIRECTORY == | ||
| - | The INDEX_DIRECTORY option declares the directory to contain the Omnidex indexes. This is not a SQL Server 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 a SQL Server setting, but rather a 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 75: | Line 75: | ||
| The extracted CREATE statements represent the best translations that can be automatically generated from SQL Server; however, these statements may require edits by the administrator. Edits that may be required include: | The extracted CREATE statements represent the best translations that can be automatically generated from SQL Server; however, these statements may require edits by the administrator. Edits that may be required include: | ||
| - | * SQLServer object names, such as tables, columns, constraints or indexes, are reduced to 32 bytes in length for use in Omnidex. | + | * SQL Server object names, such as tables, columns, constraints or indexes, are reduced to 32 bytes in length for use in Omnidex. |
| * SQL Server National Character datatypes, which are commonly used to store Unicode data, are shown as CHARACTER or STRING datatype, as these are the most universal datatypes in an Omnidex application. If necessary, these can be changed to Omnidex NCHARACTER or NSTRING datatypes. | * SQL Server National Character datatypes, which are commonly used to store Unicode data, are shown as CHARACTER or STRING datatype, as these are the most universal datatypes in an Omnidex application. If necessary, these can be changed to Omnidex NCHARACTER or NSTRING datatypes. | ||
| - | * Depending on the configuration of the SQLServer database, some constraint information may not be available and must be added manually." | + | * Depending on the configuration of the SQL Server database, some constraint information may not be available and must be added manually." |
| === 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 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. |