solidDB Help : solidDB reference : Server-side configuration parameters : SQL section
  
SQL section
The following table describes the parameters that can be used in the [SQL] section of the server-side solid.ini file.
For a description of the access modes, see Access mode and persistence of parameter modifications.
 
[SQL]
Description
Factory value
Access mode
AllowDuplicateIndex
If set to yes, duplicate index definitions are allowed.
This parameter provides compatibility with earlier versions. In solidDB versions prior to 4.5, it was possible to create duplicate indexes.
no
RO
AllowUserDDLPriv
If set to no, new users do not have DDL privileges.
Starting the solidDB server with the setting AllowUserDDLPriv=no does not alter the DDL privileges of existing users. The setting only prevents new users from executing DDL.
yes
RW/
Startup
AuditTrailEnabled
If set to yes, the audit trail is enabled.
no
RO
CharPadding
If set to yes, solidDB enforces SQL standard padding of CHAR values with blanks (right-filled) to the length defined for the column.
If set to no, the blanks are discarded.
The value of the parameter does not affect comparisons (where blanks are always discarded).
Notes
▪ This parameter is effective only when using ODBC or JDBC drivers and not when using solidDB SQL Editor (solsql).
▪ This parameter is not effective in Unicode databases (General.InternalCharEncoding=UTF8).
no
RO
ConvertOrsToUnionsCount
Maximum number of OR operations that can be converted to UNION operations.
This parameter does not force the optimizer to convert OR operations to UNION operations; it only sets a maximum limit on the number of OR operations that the server can convert to UNION operations.
10
RO
CursorCloseAtTransEnd
If set to yes, the solidDB ODBC driver closes all the cursors opened from the user connection when a commit is called with SqlTransact from this connection.
If set to no, the cursors are kept open.
yes
RO
DecFloatPrecision16
If set to yes, the precision of the decimal float data type is limited to 16 (same as in solidDB version 4.5 and earlier).
In storage, the decimal float type is inflicted by the column type specification "DECIMAL" (without scale and precision).
Also, expressions involving DECIMAL or NUMERIC data types can produce decimal float values.
If set to no, the precision of the decimal float data type is 52.
no
RO
EmulateOldTimestampDiff
If set to yes, the old TIMESTAMPDIFF behavior is emulated by the server.
This old behavior returns the integer number of intervals of type interval by which timestamp_exp2 is greater than timestamp_exp1. Otherwise, the default is the new behavior which returns the integer number of interval as the amount of full units between timestamp_exp1 and timestamp_exp2.
no
RW/
Startup
EnableHints
If set to no, hints are disabled.
For details on hints, see Using optimizer hints.
yes
RW/
Startup
ExecuteNodataODBC3Behaviour
If set to no, when the execution of a DELETE or UPDATE statement does not affect any rows, the statement returns SQL_SUCCESS. This is the ODBC v.2 behavior.
If set to yes, the SQLSTATE returns SQL_NO_DATA in those situations, which conforms to ODBC v.3.
no
RO
Info
Sets the level of informational messages [0-8] printed from the server.
Possible values range from 0 (no info) to 8 (all info).
Information is written into the file that is defined by the parameter InfoFileName, or into soltrace.out if InfoFileName is not defined.
0
RW/
Startup
InfoFileFlush
If set to yes, the info file is flushed after every write operation.
yes
RW/
Startup
InfoFileName
File name and path (optional) for informational messages.
If included, the path can be an absolute path or relative to the solidDB working directory and must use the conventions of your operating system. For example, in Windows environments, if the path contains white space characters, the path must be enclosed in double quotation marks. If the server runs on a UNIX operating system, path separators must be slashes instead of backslashes.
Because the soltrace.out file can contain information from several sources, you should set InfoFileName to another name if you set the Info or SQLInfo parameters to a number that is larger than 0.
soltrace.out
RW/
Startup
InfoFileSize
Maximum size (in bytes) of the info file.
Follow the value with K (to specify a value in KB), M (to specify a value in MB), or G (to specify a value in GB).
100 MB
RW/
Startup
IsolationLevel
Isolation level.
The following values are valid:
▪ 3 (SERIALIZABLE)
▪ 2 (REPEATABLE READ)
▪ 1 (READ COMMITTED)
For more information about transaction isolation levels, see SET ISOLATION LEVEL and Controlling transaction isolation levels.
Important In-memory tables support only the READ COMMITTED and REPEATABLE READ isolation levels.
1
RW
Latin1CaseSemantics
If set to no, uppercase/lowercase conversions are disabled for characters with decimal value between 126 and 256.
yes
RW/
Startup
MaxBlobExpressionSize
Maximum length (in kilobytes) of character string to use in string operations.
Follow the value with M (to specify a value in MB). For example: MaxBlobExpressionSize=2M
Certain string operations use only the first N bytes of a character value, not the entire value. For example, the LOCATE() operation checks only the first N bytes of the string. If you want to tell the server to check further into (or less far into) long strings, you can set this parameter.
This parameter applies to all the character data types, including CHAR, VARCHAR, LONG VARCHAR, WCHAR, WVARCHAR, and LONG WVARCHAR. Since the Wide character data types use 2 bytes per character, the number of characters searched is half the number of bytes.
For example, if you set MaxBlobExpressionSize=64, then the first 32KB characters of Wide character data types will be searched.
1024 (1MB)
RW/
Startup
MaxNestedProcedures
Maximum number of nested procedures allowed.
Depending on the operating system, if the parameter value is too large, the server stack might become insufficient.
16
RW/
Startup
MaxNestedTriggers
Maximum number of nested triggers allowed.
This maximum number includes both direct and indirect nesting, so both
A calling A calling A
and
A calling B calling A
are counted as three nested triggers.
16
RW/
Startup
NumericPadding
If set to yes, output of DECIMAL and NUMERIC are zero-right-padded up to the specified scale.
no
RO
ParallelSQLEnabled
If set to yes, parallel database engine reads are enabled for SQL statements.
no
RW/
Startup
PreferExactNumericFunctions
If set to yes, the precision of SUM() and AVG() type functions is affected in the following ways:
▪ If the argument of a SUM() or AVG() function is of an exact numeric datatype (TINYINT, SMALLINT, INTEGER, BIGINT, NUMERIC or DECIMAL), the function returns the result in DECIMAL data type. The default precision of DECIMAL is 52 and the scale is floating.
▪ Functions FLOOR() CEILING() and ABS() return their result in the same data type as the argument.
Note This parameter can be set only by editing the solid.ini file.
no
RW/
Startup
ProcedureCache
Maximum number of prepared procedures per connection.
10
RW/
Startup
ReplanCheckCounter
Minimum number of changed rows in a table that causes a query to be replanned (if the percentage that is specified with the ReplanClearPercent parameter is also reached).
1000000
RO
ReplanClearPercent
Minimum percentage of changed rows in a table that causes a query to be replanned (if the number of rows that is specified with the ReplanCheckCounter parameter is also reached).
20
RO
SampleCheckCounter
Minimum number of changed rows in a table that triggers sample recollection (if the percentage that is specified with the SampleClearPercent parameter is also reached).
1000000
RO
SampleClearPercent
Minimum percentage of changed rows in a table that triggers sample recollection (if the number of rows that is specified with the SampleCheckCounter parameter is also reached).
20
RO
SimpleOptimizerRules
If set to yes, simple optimization rules are used instead of using full optimization rules.
no
RO
SimpleSQLOpt
If set to yes, the server uses a simple SQL optimization feature that increases performance with specific types of single-table SQL queries.
Performance improvements apply to SELECT, DELETE, and UPDATE statements. The feature does not apply to INSERT statements.
yes
RO
SortArraySize
Size of the array (in rows) that SQL uses when ordering the result set of a query.
For example, if you specify a value of 1000, the server will create an array big enough to sort 1000 rows of data.
4000
RW
SQLInfo
Level of informational SQL level messages [0-8] (0=no info, 8=all info).
Information is written to a file that is specified by the InfoFileName parameter.
0
RW/
Startup
TimestampDisplaySize19
If set to yes, the precision (maximum number of digits) of data type timestamp is set to 19.
In this case, the timestamp is presented as yyyy-mm-dd hh:mm:ss.
no
RO
TriggerCache
Maximum number of prepared triggers per connection.
20
RW/
Startup
UpCaseQuotedIdentifiers
If set to yes, the SQL identifiers given in double quotation marks are converted to upper case by the solidDB server.
If set to no, the upper/lower case distinction is preserved whereby uniqueness of names incorporates the case too.
yes
RW/
Startup
VolatileReplanCheckCounter
Minimum number of changed rows in a temporary table that causes a query to be replanned (if the percentage that is specified with the VolatileReplanClearPercent parameter is also reached).
1000
RO
VolatileReplanClearPercent
Minimum percentage of changed rows in a temporary table that causes a query to be replanned (if the number of rows that is specified with the VolatileReplanCheckCounter parameter is also reached).
20
RO
VolatileSampleCheckCounter
Minimum number of changed rows in a temporary table that triggers sample recollection (if the percentage that is specified with the VolatileSampleClearPercent parameter is also reached).
1000
RO
VolatileSampleClearPercent
Minimum percentage of changed rows in a temporary table that triggers sample recollection (if the number of rows that is specified with the VolatileSampleCheckCounter parameter is also reached).
20
RO
Go up to
Server-side configuration parameters