Property

Description

Alternate Collating Sequence

The ACS (Alternate Collating Sequence) file is a translation file for the range and locate expressions. This file is used in databases whose alphabetical characters are not sorted by the ANSI code. In order to do range/locate, you use the Acs file.

The ACS file lets you define separate ACS files for specific DBMSs or individual databases if they support the feature.

Zoom from the Alternate Collating Sequence (ACS) property to an Open File dialog box. Select the ACS file.

Max. Connections

Some RDBMSs, such as MSSQL, use different numbers of connections in their internal implementations.

This property controls the maximum number of connections the gateway can use. The Max. connections applies to each line in the Database repository.

The number of connections is for the Server/User-name pairs. If you have defined several databases in the Database repository, and some of them use different servers or different usernames, this number applies to each database that has a different server or user name.

The greater the number of connections the gateway uses, the better the client concurrency. However, at the same time, RDBMS resource requirements increase while server performance decreases.

Specify 0 to use the default number of connections.

Specify a number greater than 0 to set the number of connections to the databases.

Default value: 3 connections

Isolation Level

The Isolation level determines what happens during the concurrent (simultaneous) use of the same transaction. The user can change the Isolation level in the database only. Changes made in the DBMS Properties dialog box have an effect on the system. For additional, information see Isolation Level.

Relevant databases: MSSQL, DB2 and IBM i

Default values: MSSQL=0, DB2=1, IBM i=0

Check Existence

This property determines if Magic xpa will check the existence of every table it tries to access in runtime. If the table does not exist, Magic xpa will create it.

Clearing this check box will enhance performance and will prevent Magic xpa from creating tables in the database. If a specific table does not exist, an error will be given by the underlying RDBMS.
This option is recommended for the Runtime environment.

Selecting this check box will decrease performance, since Magic xpa will have to send extra SELECT statements to the DBMS each time the table is accessed.
If the table does not exist, Magic xpa will attempt to create the table in the database.
This option is recommended for the Studio environment.

Note: This property will be copied to any new database entry that belongs to the specific DBMS in the Database repository.