This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dev:sql:statements:create_database:home [2010/07/06 22:48] els |
dev:sql:statements:create_database:home [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 30: | Line 30: | ||
| ===== Discussion ===== | ===== Discussion ===== | ||
| === DATABASE database_name === | === DATABASE database_name === | ||
| - | The //database_name// uniquely identifies the database within this environment. It may be up to 32 characters long, and can contain letters, digits and the following special characters: ! @ # $ % ^ _. It must begin with a letter and is case-insensitive. The //database_name// must be unique within the environment. | + | The //database_name// uniquely identifies the database within this environment. It may be up to 32 characters long, and can contain letters, digits and the following special characters: ! @ # $ % ^ _. It must begin with a letter and is case-insensitive. The //database_name// must be unique within the environment. If //database_name// is a SQL reserved word, enclose it in double quotation marks. |
| Line 47: | Line 47: | ||
| === NODE grid_node === | === NODE grid_node === | ||
| - | The optional NODE clause is used to configure an Omnidex Grid. Nodes that were previously declared in the CREATE ENVIRONMENT statement can be referenced here, and the database configuration can be named for each node. The NODE clause is only required for databases within an Omnidex Grid that are partitioned and distributed across multiple nodes. If not using an Omnidex Grid, the NODE clause can be skipped and the underlying configuration can be specified for the entire database. | + | The optional NODE clause is used to configure an Omnidex Grid. Nodes that were previously declared in the CREATE ENVIRONMENT statement can be referenced here, and the database configuration can be named for each node. The NODE clause is only required for databases within an Omnidex Grid that are partitioned and distributed across multiple nodes. If not using an Omnidex Grid, the NODE clause can be skipped and the underlying configuration can be specified for the entire database. |
| For simple environments, the database configuration does not require NODE clauses: | For simple environments, the database configuration does not require NODE clauses: | ||
| Line 56: | Line 56: | ||
| create database "LIST" | create database "LIST" | ||
| - | type FLATFILE | + | type FILE |
| index_directory "idx" | index_directory "idx" | ||
| in "list.xml"; | in "list.xml"; | ||
| Line 75: | Line 75: | ||
| create database "LIST" | create database "LIST" | ||
| node "GRID01" | node "GRID01" | ||
| - | type FLATFILE | + | type FILE |
| index_directory "idx\grid01" | index_directory "idx\grid01" | ||
| node "GRID02" | node "GRID02" | ||
| - | type FLATFILE | + | type FILE |
| index_directory "idx\grid02" | index_directory "idx\grid02" | ||
| node "GRID03" | node "GRID03" | ||
| - | type FLATFILE | + | type FILE |
| index_directory "idx\grid03" | index_directory "idx\grid03" | ||
| node "GRID04" | node "GRID04" | ||
| - | type FLATFILE | + | type FILE |
| index_directory "idx\grid04" | index_directory "idx\grid04" | ||
| node "GRID05" | node "GRID05" | ||
| - | type FLATFILE | + | type FILE |
| index_directory "idx\grid05" | index_directory "idx\grid05" | ||
| in "list.xml"; | in "list.xml"; | ||
| Line 97: | Line 97: | ||
| Valid database types are: | Valid database types are: | ||
| - | * FLATFILE | + | * FILE |
| * ORACLE | * ORACLE | ||
| * SQLSERVER | * SQLSERVER | ||
| Line 119: | Line 119: | ||
| If no //directory// is declared, then the Omnidex index files will reside in the same directory as the Omnidex Environment File. | If no //directory// is declared, then the Omnidex index files will reside in the same directory as the Omnidex Environment File. | ||
| + | The //directory// can also be specified with an environment variable using curly braces. | ||
| + | |||
| + | <code> | ||
| + | create database "LIST" | ||
| + | type FILE | ||
| + | index_directory {$LIST_DIR} | ||
| + | </code> | ||
| === VERSION “rdbms_version” === | === VERSION “rdbms_version” === | ||
| Line 140: | Line 147: | ||
| === PHYSICAL "rdbms_string" === | === PHYSICAL "rdbms_string" === | ||
| The PHYSICAL //rdbms_string// declares RDBMS connection information and is only used with relational databases and ODBC. The //rdbms_string// varies according to database type as follows: | The PHYSICAL //rdbms_string// declares RDBMS connection information and is only used with relational databases and ODBC. The //rdbms_string// varies according to database type as follows: | ||
| - | ^ PHYSICAL_TYPES ^ Description ^ | + | ^Database Type ^Description ^ |
| - | | FLATFILES | ignored | | + | | FILE | ignored | |
| | ORACLE | The PHYSICAL clause is ignored and Oracle will use the default database for the specified user. | | | ORACLE | The PHYSICAL clause is ignored and Oracle will use the default database for the specified user. | | ||
| | ORACLE w/SQLNET | if using Oracle SQLNET, use the name of the SQLNET service and specify "SQLNETx" in the VERSION clause. | | | ORACLE w/SQLNET | if using Oracle SQLNET, use the name of the SQLNET service and specify "SQLNETx" in the VERSION clause. | | ||
| Line 226: | Line 233: | ||
| Articles: | Articles: | ||
| - | * [[admin:grids:home|Omnidex Grids]] | + | * [[admin:features:grids:home|Omnidex Grids]] |
| * [[dev:appendix:articles:dbspecific:home|Database-specific issues]] | * [[dev:appendix:articles:dbspecific:home|Database-specific issues]] | ||
| {{page>:bottom_add&nofooter&noeditbtn}} | {{page>:bottom_add&nofooter&noeditbtn}} | ||