This shows you the differences between two versions of the page.
|
dev:odxsql:commands:extract:home [2010/07/04 18:19] tdo |
dev:odxsql:commands:extract:home [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| - | ====== Omnidex SQL: EXTRACT DDL ====== | ||
| - | {{page>:sql_bar&nofooter&noeditbtn}} | ||
| - | ===== Description ===== | ||
| - | The OdxSQL EXTRACT command will Extract DDL statements (CREATE ENVIRONMENT, CREATE DATABASE, CREATE TABLE, CREATE INDEX and CREATE INDEX GROUP) from the currently connected Omnidex Environment to a file. The extracted file can then be modified with an editor and used to build another Omnidex Environment. | ||
| - | The EXTRACT command is particularly helpful in converting Omnidex Environments from previous versions that used the original Omnidex Environment Catalog syntax. | ||
| - | |||
| - | The EXTRACT command can also be used to generate INSERT, DELETE, and UPDATE statements from the existing data. This would typically be used in a testing environment. | ||
| - | |||
| - | ===== Syntax ===== | ||
| - | |||
| - | EXTRACT DDL [FOR <ENVIRONMENT [environment] | DATABASE database>] | ||
| - | [TO filespec] [ON [INSTANCE] instance] [WITH options] | ||
| - | | ||
| - | EXTRACT [CLUSTERED] <INSERTS | UPDATES | DELETE_WHERES | DELETE_EXCEPTS> | ||
| - | FROM tables [WHERE criteria] [TO filename] | ||
| - | [ON [INSTANCE] instance] [WITH options] | ||
| - | ===== Discussion ===== | ||
| - | ==== DDL ==== | ||
| - | |||
| - | |||
| - | === FOR DATABASE database_name === | ||
| - | The FOR DATABASE clause can be used to extract the DDL for a specific database should the Omnidex Environment contain multiple databases. | ||
| - | |||
| - | ==== TO filespec ==== | ||
| - | The TO filespec clause specifies the directory location and filename of the extracted statements. | ||
| - | |||
| - | If the TO filespec clause is omitted, then the file will be written to extract.sql in the current working directory. | ||
| - | |||
| - | ==== WITH options ==== | ||
| - | |||
| - | == DELETE == | ||
| - | Deletes the file specified in the TO filespec clause or the default extract.sql file if no filespec is specified in order to create a new file with the current SQL statement information. | ||
| - | |||
| - | |||
| - | ===== Examples ===== | ||
| - | |||
| - | connect myenv.xml; | ||
| - | extract ddl to myenvnew.sql; | ||
| - | |||
| - | extract ddl to myenv.sql with delete; | ||
| - | |||
| - | |||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||