Local Database Parameter
|
Explanation
|
| Database |
The name of the Mimer SQL database (required). |
| Description |
A text describing the database. |
| Directory |
The database home directory (required). |
| Users |
Maximum number of simultaneous connections allowed to the database server (recommended). |
| DBCheck |
The type of check performed after an improper shutdown of the system. All Pages is strongly recommended. Data pages are checked in the background.
0 = Index Only
1 = All Pages |
| PriorityClass |
The priority class of the server. Should be an integer in the range 0-3.
0 = Idle
1 = Normal
2 = High
3 = Real-time Further information about priorities may be found in the Win32 documentation for the routine SetPriorityClass. |
| RequestThreads |
An integer specifying the number of request threads in the database server. Each request thread can handle one concurrent application request. If there are many long requests this parameter may have to be increased form the default. |
| RequestPriority |
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 Further information about priorities may be found in the Win32 documentation for the routine SetThreadPriority. |
| BackgroundThreads |
An integer specifying the number of background threads. If there are many large transactions and/or shadowing is used, the number of threads may need to be increased. Actually, it is more important to give the background threads sufficient priority rather than increase the number of threads. The number of background threads determine how many databases are checked in parallel. Half of the threads are used for this. |
| BackgroundPriority |
The priority class of the background threads. Should be an integer in the range 0-6. See RequestPriority for the specific values. It is recommended that this parameter is equal to or one higher than the value for RequestPriority. |
| StartupType |
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 |
| AutoRestart |
An integer value which is specified if the server is to be started manually or started automatically after a failure. 0 = Manual restart
1 = Automatic restart |
| Pages2K |
An integer specifying the number of 2K pages in the bufferpool. |
| Pages16K |
An integer specifying the number of 16K pages in the bufferpool. |
| Pages64K |
An integer specifying the number of 64K pages in the bufferpool. |
| SQLPool |
The initial size of the SQL-pool in bytes. The SQL-pool contains information about users logged in, compiled SQL statements and so on. |
| MaxSQLPool |
If you want to limit the amount of memory the database server allocates, this parameter specifies the maximum number of bytes that the server allocates for the SQL-pool. |
| ActTrans |
Maximum number of transactions that can be active in the database server including background threads processing. |
| Databanks |
Maximum number of allowed databanks. |
| Tables |
Maximum number of open tables allowed. |
| CommBuffSize |
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. The default size is 64K. Any buffer size specified is rounded up to the nearest 64K boundary. |
| TcpPort |
This can be either a port number, such as 1360 or one of the strings <Name Server> or <Disabled>. If <Name Server> is used, incoming TCP connections are handled by a separate TCP server process and then handed over to the correct database server. |
| NamedPipe |
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. As for TcpPort the strings <Name Server> or <Disabled> may also be used. |
| RmGuid |
This is a unique identifier identifying the database server used for inter-operating with Microsoft Distributed Transaction Coordinator. Do not specify RmGuid unless you are renaming a database server, in which case the original RmGuid should be kept. |
| DumpPath |
This is a path to the directory under which database server dump directories and files will be placed. Typically these are placed below the database home directory. |
