Previous Topic Next topic Print topic


ACUFH Configuration File Variables

Before running Database Connectors, you must set the A_CONFIG environment variable to the name of the ACUFH configuration file. You may want to make and use a personalized copy of the ACUFH configuration file to avoid impacting other users. You could use the A_CONFIG environment variable to identify a personal ACUFH configuration file. For example:

SET A_CONFIG=directory name\file name

defines a configuration file with the name of your choice in the directory of your choice.

This section lists the ACUFH configuration file variables that are specific to MSSQL. ACUFH configuration file variables that are generally applicable to any RDBMS with which Database Connectors communicates are discussed in the section ACUFH configuration file in the chapter Runtime Configuration. For detailed descriptions of these variables, see the Reference > Configuration Variables section of your Database Connectors documentation. A minimal required set of configuration variables is:

and either:

or:

For information on dynamic redirection to a custom file handler, see the section Enabling Dynamic Redirection to a Custom File Handler.

Variable Description
A_MSSQL_ADD_IDENTITY Adds an extra column to any table created by the Connector
A_MSSQL_ADD_TIMESTAMP Ensures that modifications made to a row are not overwriting someone else's changes
A_MSSQL_APPROLE_NAME Allows the Connector to use approles
A_MSSQL_APPROLE_PASSWD Allows the Connector to use approles
A_MSSQL_CURSOR_OPTION_1, A_MSSQL_CURSOR_OPTION_2, A_MSSQL_CURSOR_OPTION_3 Allow you to fine-tune the declaration of cursors in the Connector
A_MSSQL_DATABASE Specifies the name of the particular database to be accessed
A_MSSQL_DEADLOCK_LOOPS Can be used to instruct the Connector to re-execute an INSERT statement
A_MSSQL_DEFAULT_CONNECTION Specifies the name of the server to which the run time system connects
A_MSSQL_DEFAULT_OWNER Specifies the name of the user of a table
A_MSSQL_FAST_ACCESS Files opened while this variable is set to a nonzero value are optimized for forward sequential access
A_MSSQL_LOCK_DB Specifies the name of the database that holds the lock table
A_MSSQL_LOGIN Indicates the user name under which you want to connect to the database system
A_MSSQL_MAX_CHARACTERS Indicates the maximum number of bytes the Connector allows in a table row
A_MSSQL_MAX_COLUMNS Indicates the maximum number of columns the Connector allows in a table
A_MSSQL_NATIVE_LOCK_TIMEOUT One of two locking methods available with the Connector
A_MSSQL_NO_COUNT_CHECK Causes the interface not to check that a record was updated
A_MSSQL_NO_DBID Causes the interface to use a Database ID of "0", instead of the actual ID of the database
A_MSSQL_NO_RECORD_LOCKS Causes all READS to be treated as READ NO LOCK
A_MSSQL_NO_TABLE_LOCKS Causes the interface to not use the AcuOpenTables1 table, which causes all table locking to be disabled
A_MSSQL_NO_23_ON_START Causes START not to detect whether records actually exist
A_MSSQL_NT_AUTHENTICATION Indicates whether MSSQL authenticates users based on their Windows login
A_MSSQL_PACKETSIZE Sets the size of network packets
A_MSSQL_PASSWD Set to the password assigned to the database account associated with the user name specified by A_MSSQL_LOGIN
A_MSSQL_ROWCOUNT Determines how many rows are returned by a SELECT statement sent to the server
A_MSSQL_SELECT_KEY_ONLY Directs the interface to select key columns only when searching for records
A_MSSQL_SKIP_ALTERNATE_KEYS Determines whether alternate keys are used to form indexes during table creation
A_MSSQL_TRANSLATE_TO_ANSI Causes the Connector to call the same translation function used by the Windows run time system to translate characters going to the server into the OEM character set, and to translate characters coming from the server to ANSI
A_MSSQL_UNLOCK_ON_EXECUTE Causes all invocations of I$IO using the EXECUTE opcode to unlock all records
A_MSSQL_USE_DROPDOWN_QUERIES Causes selects sent to the database to be of the drop-down variety, instead of a single large query
Previous Topic Next topic Print topic