Administrator Guide : Gateway Configuration Variables : How Gateway Parameters are Configured : Microsoft SQL Only
 
Share this page                  
Microsoft SQL Only
The following parameters apply only to the Microsoft SQL Server gateway.
hex_len
ii.hostname.gateway.mssql.hex_len: integer
Specifies the maximum number of input bytes the hex function will process. The output length will be two times the size of the input length.
Default: 30 bytes
multiple_open_cursors
ii.hostname.gateway.mssql.multiple_open_cursors: string
Specifies whether support for multiple open cursors is enabled. Usage of multiple open cursors in Microsoft SQL Server can lead to performance problems in the DBMS. If you do not need to use multiple open cursors in your application, set this parameter to OFF (CBF) or deselect the check box (VCBF). This option should be used with caution as it requires an in-depth understanding of the application and the effects of setting this parameter on the specific application.
Valid values for the multiple_open_cursors parameter are as follows:
Value
Behavior
ON (CBF);
check box selected (VCBF)
Enables support for multiple open cursors.
OFF (CBF);
check box unselected (VCBF)
Disables support for multiple open cursors for performance-valid only if applications connecting to the gateway do not make use of multiple open cursors.
Default: ON
union_zerolength_column_padding
ii.hostname.gateway.mssql.union_zerolength_column_padding: bytes
Forces the length of a UNION select result.
Prior to MS SQL Server 2005, the result of a special-syntaxed UNION select is truncated to zero length if an empty string ('') is specified in the first select and host variables are used in the WHERE clause. UNION_ZEROLENGTH_COLUMN_PADDING was created to force the length of the result and offset the zero length truncation problem. This parameter has no effect on SQL Server 2005 or above.
Default: 255
Maximum: 8000