5.1 Mimer SQL Specific Parameters and Commands
To set up and configure a Mimer SQL database, the parameters and commands below may be specified in a call to SQLConfigDataSource. If a parameter is not specified, the system uses an appropriate default.
You can find additional information about these parameters and commands through the help facility in the Mimer Administrator. Many of the parameters are also described in the Mimer SQL System Management Handbook.
The parameters and commands are divided into the following groups:
- Data source parameters, see Data Source Parameters.
- Local database parameters, see Local Database Parameters.
- Local database server commands, see Local Database Server Commands.
- Remote database parameters, see Remote Database Parameters.
- License key parameters, see License Key Parameters.
To create both a data source and a remote definition, you specify parameters from the two groups together. It is not possible to combine remote parameters with local parameters or commands.
5.1.1 Data Source Parameters
5.1.2 Local Database Parameters
The priority class of the server. Should be an integer in the range 0-3.
0 = Idle
1 = Normal
2 = High
3 = Real-time
An integer specifying the number of request threads in the database server. Each request thread can handle one concurrent application request.
The priority class of the kernel threads. Should be an integer in the range 0-6.
0 = Idle
1 = Lowest
2 = BelowNormal
3 = Normal
4 = AboveNormal
5 = Highest
6 = TimeCritical
An integer value which is specified if the server is to be disabled, started manually or started automatically after a system reboot.
0 = Autostart
1 = Manual start
2 = Disabled
An integer value which is specified if the server is to be started manually or started automatically after a failure.
This is the size of local communication buffers (specified in bytes). If communication packages exceed this size, several calls are made to the database server. This may increase overhead.
This is the name of the named pipe the database server uses to listen for incoming requests. The default is a named pipe with the same name as the database server.
This is a unique identifier identifying the database server used for inter-operating with Microsoft Distributed Transaction Coordinator.
5.1.3 Local Database Server Commands
The parameters to the command correspond to the command line arguments specified when using the system databank generation utility (SDBGEN).
This is further described in Defining a Database.
This is further described in Upgrading a Mimer SQL Installation.
5.1.4 Remote Database Parameters
For named pipes, this is the name of the pipe that the database server is waiting for incoming connections on.
The default for version 8 and version 9 servers is to listen on a pipe with the same name as the database. In previous versions, the default was MIMER. This means that you must know if the server is a version 7 or version 8 or 9 database server. The default for version 8 and 9 clients is to use the database name.
5.1.5 License Key Parameters
Mimer Information Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40