Create Database Through DSN Setup

Element	Description
Database Name	The name for the database that you want to appear in the database listings. For example, the database name you see in PSQL Control Center. Note: The database name cannot be the same as an existing database name.
Integrity Enforced	Specifies whether integrity constraints (security, RI, and triggers) are enforced on the database. These constraints apply to Btrieve access to the data files as well as ODBC/SQL access. For additional information, see Interactions Between Btrieve and Relational Constraints in Advanced Operations Guide.
Bound	Indicates whether or not the database is bound. Binding a database prevents the DDFs or data files from being used in another database and prevents a data file from having two or more different table definitions within the same database. For more information about bound databases, refer to Bound Database versus Integrity Enforced in Advanced Operations Guide.
Long Metadata (V2 metadata)	Specifies whether you want the database to use version 1 (V1) or version 2 (V2) metadata. The PSQL Engine supports two versions of metadata, referred to as version 1 (V1) and version 2 (V2). Metadata version is a property of the database, which means that it applies to all tables within that database and is recorded in the dbnames.cfg file. A database cannot use some tables with V1 metadata and others with V2 metadata. Metadata from the two versions cannot interact. For additional information, see PSQL Metadata in the SQL Engine Reference.
Code Page	Specifies the code page that applies to the database data and metadata. This property is stored in DBNAMES.cfg. The default code page is “server default,” meaning the operating system code page on the server where the database engine is running. Note that database code page and client encoding are separate but interrelated. See Database Code Page and Client Encoding in Advanced Operations Guide.
Btrieve security policy	Specifies the security model to use for the transactional interface.See Available Models for the MicroKernel Engine in Advanced Operations Guide.
Dictionary Location	This location specifies where the dictionary files (DDFs) reside on physical storage. This location must be on the same server to which you are connected (and where the database engine is running). The location must be formatted as though you are working directly at the server machine. Enter a path in the form drive:\path, where drive is a drive letter on the server.
Data File Location	This location specifies where the data files reside on physical storage. The Add button lets you add locations to the list. The Delete button lets you remove locations from the list. The locations must be on the same server where the database engine is running. Specify the location in the same manner as for the dictionary locations.

The name for the database that you want to appear in the database listings. For example, the database name you see in PSQL Control Center.

Note: The database name cannot be the same as an existing database name.

Integrity Enforced

Specifies whether integrity constraints (security, RI, and triggers) are enforced on the database. These constraints apply to Btrieve access to the data files as well as ODBC/SQL access.

For additional information, see Interactions Between Btrieve and Relational Constraints in Advanced Operations Guide.

Bound

Indicates whether or not the database is bound. Binding a database prevents the DDFs or data files from being used in another database and prevents a data file from having two or more different table definitions within the same database.

For more information about bound databases, refer to Bound Database versus Integrity Enforced in Advanced Operations Guide.

Long Metadata (V2 metadata)

Specifies whether you want the database to use version 1 (V1) or version 2 (V2) metadata.

The PSQL Engine supports two versions of metadata, referred to as version 1 (V1) and version 2 (V2). Metadata version is a property of the database, which means that it applies to all tables within that database and is recorded in the dbnames.cfg file. A database cannot use some tables with V1 metadata and others with V2 metadata. Metadata from the two versions cannot interact.

For additional information, see PSQL Metadata in the SQL Engine Reference.

Code Page

Specifies the code page that applies to the database data and metadata. This property is stored in DBNAMES.cfg.

The default code page is “server default,” meaning the operating system code page on the server where the database engine is running.

Note that database code page and client encoding are separate but interrelated. See Database Code Page and Client Encoding in Advanced Operations Guide.

Btrieve security policy

Specifies the security model to use for the transactional interface.See Available Models for the MicroKernel Engine in Advanced Operations Guide.

Dictionary Location

This location specifies where the dictionary files (DDFs) reside on physical storage. This location must be on the same server to which you are connected (and where the database engine is running). The location must be formatted as though you are working directly at the server machine.

Enter a path in the form drive:\path, where drive is a drive letter on the server.

Data File Location

This location specifies where the data files reside on physical storage. The Add button lets you add locations to the list. The Delete button lets you remove locations from the list. The locations must be on the same server where the database engine is running.

Specify the location in the same manner as for the dictionary locations.