Copyright: Copyright © 1982-1998 Pervasive Software Inc. All


Bind
Makes the database a bound database.

NOTE: To bind successfully, an existing database cannot reference dictionary or data files referenced by another named database. If your database does share dictionary or data files, you must ensure that all named databases sharing the dictionary files are unbound.


Bound
Displays when the database is bound. For more information about bound databases, refer to the Pervasive.SQL Programmer's Guide.


Categories List Box

Contains the categories of settings for the component you have selected. Select the category for which you want to view or modify settings.


Category Description Text

Contains an overview of the selected settings category.


Changing Settings

Following is a description of each of the controls on the Setup window and how you use them to change settings.

Components List Box

Categories List Box

Category Description Text

Settings List Box

Setting Description Text

Settings Group

Tip

*	Any settings labeled Advanced are intended for experienced users who need to perform fine-tuning or debugging operations. The default values for these settings are sufficient for most installations.

Here are the different types of settings and the controls used to set them:

Setting Type	Controls
Boolean:	Default Current ( On / Off )
Numeric:	Default Minimum Maximum Current
Selection:	Default Selection ( List or radio buttons)
Directory/File Path:	Default Current (Path)
Others:	Some settings, like tracing, have a set of controls which are specific to only that setting.
Save Button

Saves all changed settings to the configuration database. In most cases you must unload and restart the component for the setting changes to take affect.

Exit Button

Closes the Setup Utility without saving any changed settings.

Help Button

Shows this help screen.


Check
Determines whether the entry for this database in the DBNAMES.CFG file accurately reflects the existing dictionary and data files.


Components List Box

Contains the database components which you can configure. Select the component for which you want to view or modify settings.


Configuring Components on Remote Servers

The Setup Utility allows you to connect to remote servers to configure the components on that remote server. You can remotely configure the following components:

*	MicroKernel Database Engine

*	Btrieve Communications Manager

*	Scalable SQL Engine

*	Scalable SQL Communications Manager

When the Setup Utility is run, it first looks for components on the local machine. If it finds no components it can configure on the local machine, the Component List Box will contain no entries.

Related Topics

Connecting to a Remote Server


Connecting to a Remote Server
To connect to a Remote Server

1  Click the Connect button.

2  Enter the name of the server to which you want to connect.

When you click the OK button, an attempt to make a connection to the names server will be made. If the connection succeeds, the Setup Utility will look for components on the remote machine.

Tip

*	If no components on the remote server can be found, the Component List Box will contain no entries.


Contents

Introduction

Configuring Components on Remote Servers

Maintaining Named Databases

How To...

Connect to a remote server

Create a bound database

Delete a named database

Modify a named database

Changing Settings


Create
Allows you to create a new named database.


Create a bound database
To create a bound database:

1	In the Database Name field, enter the name of the database. Do not specify a database name that includes spaces. The SQL Interface displays the name only up to the embedded space, so the name My DB is advertised as My.

2	By default, Integrity Enforced setting is enabled. This setting determines whether Pervasive.SQL enforces integrity constraints (including security, referential integrity, and triggers) on the database, regardless of whether the database is bound.

In general, you should not disable integrity enforcement. However, you may want to suspend integrity constraints to facilitate bulk data loads.

3	By default, the Bound setting is enabled which determines that a database is bound. When you create a bound database, the SQL Interface creates the appropriate dictionary files.

You cannot create a bound database for which the dictionary files already exist. If you have existing dictionary files, first create an unbound database, then use the Bind button in the Maintain Named Databases dialog box.

4	Specify the dictionary location for the database in the Dictionary Location field. This location must be on the same server to which you are connected.

For NetWare, enter a path in the form of vol:\path. For Windows NT, enter a path in the form drive:\path where drive should be a local drive letter.

5	Specify the location of the data file(s) in the Data File Locations field. Click Add to enter a location in the Location pop-up dialog.

If you are specifying paths to data files on this server, specify paths the same as you did in the Dictionary Location field. If you are entering paths to data files on another server, specify the full name. For NetWare, specify the path in the form \\server\vol1\path (UNC format) or server\vol1:\path; for Windows NT and Windows 9X, specify the path in the form \\server\sharename\path.

You can click Delete if you decide not include a specific data file location.

6	Click OK to create the named database and close the dialog box, or click Cancel to close the dialog box without saving changes.

Related Topic

Modify a named database

Delete a named database

Maintain named databases


Data File Locations
Displays the location of data files for the database.


Database Names
Lists the available named databases.


Delete
Deletes the database name from the DBNAMES.CFG file. For bound databases, this operation also deletes the associated dictionary files. For unbound databases, this operation does not delete any files.


Delete a named database
To delete a named database

Highlight the database name in the Database Names list and click Delete. The named database is removed from the list of database names.

Related Topics

Create a bound database

Modify a named database

Maintain named databases


Dictionary Location
Displays the location of the DDF files for the selected database name.


Integrity Enforced
Displays whether Pervasive.SQL is enforcing integrity constraints (including security, referential integrity, and triggers) on the database.


Introduction

The Setup Utility enables you to modify the settings for a number of Pervasive components. These components include the MicroKernel Database Engine, the Scalable SQL Engine, the Scalable SQL Communications Manager, the Btrieve Communications Manager and the local Requester components. The settings for these components are stored in a configuration database suitable for the platform. The first time components are loaded, they generate default values in the configuration database. These defaults are adequate for many installations but may need to be changed if:

*	Your Btrieve or Scalable SQL-based applications require that you adjust the settings. Refer to the documentation included with the application for more information.

*	You want to optimize the settings so that the components provide the services you need without using more memory than necessary. (The memory requirements stated in the manual provide guidelines for optimizing use of your computer's resources.)


Maintaining Named Databases

A named database has a logical name that allows users to identify it without knowing its actual location. When you name a database, you associate that name with a particular dictionary directory path and one or more data file paths. When you log in to the SQL Interface using a database name, the SQL Interface uses the name to find the databases dictionary and data files. A named database enables you to do the following:

*	Define triggers

*	Define primary and foreign keys

*	Bind a database

*	Suspend a databases integrity constraints

*	You use the Maintain Named Database feature to bind and name databases.

Maintain Named Database Dialog Box Elements

Database Names

Dictionary Location

Integrity Enforced

Bound

Data File Locations

Create

Modify

Delete

Bind

Unbind

Check

Related Topics

Create a bound database

Modify a named database

Delete a named database


Modify
Allows you to change the properties of the current database.


Modify a named database
To modify a named database

1	Add or modify data file locations.

You cannot modify the Database Name or Dictionary Location for bound databases or for databases that contain triggers or foreign keys.

2	Click OK to save your modifications. Otherwise, click Cancel to close this dialog without saving changes.

Related Topics

Create a bound database

Delete a named database

Maintain named databases


Setting Description Text

Contains an overview description of the selected setting.


Settings Group

Contains controls for the current setting. The controls vary depending upon the type of setting. The current value is the only editable value.


Settings List Box

Contains the configurable settings for the selected category. Select the setting which you want to view or modify.


Unbind
Makes the database an unbound database and changes the status of each dictionary and data file to unbound.

NOTE: Because the engine automatically stamps a file as bound if it has a trigger, a foreign key, or a primary key referenced by a foreign key, you may unbind the database, but have some files that remain bound.

For more information about bound databases, refer to the Pervasive.SQL Programmers Guide.