New and changed configuration parameters for Adaptive Server 15.0.1
| Configuration parameter | Description |
|---|---|
| startup delay | Controls when RepAgent is started during the server start. By default, RepAgent starts at the same time as Adaptive Server. Adaptive Server writes a message to the error log stating the wait time. |
| enable literal autoparam | Enables and disables literal server-wide parameterization. |
| cis idle connection timeout. |
configures Adaptive Server to check for CIS connections to any remote server that have been unused longer than the specified number of seconds. Adaptive Server deletes the unused connections and reallocates their resources. Although the number you specify is in seconds, the housekeeper task wakes up at most once a minute, so idle connections may be idle for much longer than the configured value. Adaptive Server does not drop idle connections if a transaction is active on the connection, and reestablishes the connection automatically if the user executes any command that accesses the connection. |
| sproc optimize timeout limit | Specifies the amount of time Adaptive Server can spend optimizing a system procedure as a fraction of the estimated execution time. |
| Configuration parameter | Description of change |
|---|---|
| optimization timeout limit | The range of values available for optimization timeout limit has changed. With version 15.0.1, it is 0 - 1000. A value of 0 indicates no optimization timeout. |
| max parallel degree | If max parallel degree is set to 1 (enabled), Adaptive Server forces serial query execution and the optimizer may select plans with a higher parallel degree than if it is disabled. |
| number of worker processes | If you have not configured number of worker processes for a sufficient number of threads from the worker thread pool, Adaptive Server adjusts query plans at runtime to use fewer worker threads. If Adaptive Server cannot adjust the queries at run-time, the queries recompile serially. However, alter table and execute immediate commands are aborted if they do not have sufficient worker threads. |
See the System Administration Guide: Volume 1.