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:44] els |
dev:sql:statements:create_database:home [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | + | ^ Omnidex SQL Quicklinks ^^^^^ |
| + | |[[dev:sql:overview | Overview ]] | [[dev:sql:statements:home | Statements ]] | [[ dev:sql:functions:home | Functions ]] | [[ dev:sql:examples:home | Examples ]] | [[dev:sql:home | Quick Reference ]] | | ||
| ====== Omnidex SQL: CREATE DATABASE ====== | ====== Omnidex SQL: CREATE DATABASE ====== | ||
| - | {{page>:sql_bar&nofooter&noeditbtn}} | ||
| - | ^ See Also: ^ [[dev:sql:statements:create_environment:home| Create Environment ]] ^ [[dev:sql:statements:create_table:home | Create Table]] ^ [[dev:sql:statements:create_index:home | Create Index ]] ^ [[dev:sql:statements:drop_database:home | Drop Database ]] ^ | ||
| ===== Description ===== | ===== Description ===== | ||
| The CREATE DATABASE statement declares a database in an Omnidex Environment File. Once one or more databases and their respective tables have been declared in an environment, they can be indexed and retrieved using SQL statements. | The CREATE DATABASE statement declares a database in an Omnidex Environment File. Once one or more databases and their respective tables have been declared in an environment, they can be indexed and retrieved using SQL statements. | ||
| Line 31: | 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 48: | 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 57: | 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 76: | 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 98: | Line 97: | ||
| Valid database types are: | Valid database types are: | ||
| - | * FLATFILE | + | * FILE |
| * ORACLE | * ORACLE | ||
| * SQLSERVER | * SQLSERVER | ||
| Line 105: | Line 104: | ||
| When a database is spread across multiple nodes of an Omnidex Grid, the PHYSICAL clause is declared for each node. At present, the //database_type// must be the same across all nodes; however, support for different database types for each node may be supported in the future. | When a database is spread across multiple nodes of an Omnidex Grid, the PHYSICAL clause is declared for each node. At present, the //database_type// must be the same across all nodes; however, support for different database types for each node may be supported in the future. | ||
| - | == SUBTYPE odbc_subtype == | + | === SUBTYPE odbc_subtype === |
| The SUBTYPE setting within the TYPE clause is used to specify a subtype for ODBC databases. | The SUBTYPE setting within the TYPE clause is used to specify a subtype for ODBC databases. | ||
| Line 120: | 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 141: | 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. | | ||
| | SQLSERVER | The PHYSICAL clause contains the ODBC connection information. For File DSNs, use "FILEDSN=file_dsn_filespec". For System and User DSNs, use "DSN=dsn_name" or just "dsn_name" where dsn_name is the data source name set up in the Windows ODBC Administrator program. | | | SQLSERVER | The PHYSICAL clause contains the ODBC connection information. For File DSNs, use "FILEDSN=file_dsn_filespec". For System and User DSNs, use "DSN=dsn_name" or just "dsn_name" where dsn_name is the data source name set up in the Windows ODBC Administrator program. | | ||
| | ODBC | The PHYSICAL clause contains the ODBC connection information. For File DSNs, use "FILEDSN=file_dsn_filespec". For System and User DSNs, use "DSN=dsn_name" or just "dsn_name" where dsn_name is the data source name set up in the Windows ODBC Administrator program. | | | ODBC | The PHYSICAL clause contains the ODBC connection information. For File DSNs, use "FILEDSN=file_dsn_filespec". For System and User DSNs, use "DSN=dsn_name" or just "dsn_name" where dsn_name is the data source name set up in the Windows ODBC Administrator program. | | ||
| - | ==== USER “rdbms_user” PASSWORD “user_password” ==== | + | |
| + | === USER “rdbms_user” PASSWORD “user_password” === | ||
| The USER and PASSWORD clauses are used to provide a valid RDBMS database user and password to be used for Omnidex to access the underlying RDBMS data source. The USER and PASSWORD clauses are required for Oracle, and are otherwise optional. | The USER and PASSWORD clauses are used to provide a valid RDBMS database user and password to be used for Omnidex to access the underlying RDBMS data source. The USER and PASSWORD clauses are required for Oracle, and are otherwise optional. | ||
| Line 216: | Line 223: | ||
| disconnect | disconnect | ||
| </code> | </code> | ||
| + | |||
| + | ====== Additional Resources ====== | ||
| + | See also: | ||
| + | * [[dev:sql:statements:create_environment:home|CREATE ENVIRONMENT]] | ||
| + | * [[dev:sql:statements:create_table:home|CREATE TABLE]] | ||
| + | * [[dev:sql:statements:create_index:home|CREATE INDEX]] | ||
| + | * [[dev:sql:statements:update_indexes:home|UPDATE INDEXES]] | ||
| + | |||
| + | Articles: | ||
| + | |||
| + | * [[admin:features:grids:home|Omnidex Grids]] | ||
| + | * [[dev:appendix:articles:dbspecific:home|Database-specific issues]] | ||
| {{page>:bottom_add&nofooter&noeditbtn}} | {{page>:bottom_add&nofooter&noeditbtn}} | ||