The following configuration parameters are unique to Component Integration Services:
enable file access
enable full-text search
max cis remote connections
cis bulk insert batch size
cis bulk insert array size
cis connect timeout
cis cursor rows
cis packet size
cis rpc handling
Use this parameter with sp_configure to enable Component Integration Services as follows:
Log into Adaptive Server as the System Administrator and issue the following command:
sp_configure "enable cis", 1
Restart Adaptive Server.
Issuing the command sp_configure "enable cis", 0 disables Component Integration Services after restarting the server.
This configuration parameter enables access through proxy tables to eXternal File System. Requires a license for ASE_XFS.
This configuration parameter enables Enhances Full-Text Search services. Requires a license for ASE_EFTS.
This configuration property is no longer needed, as RDES structs will be allocated as needed from shared memory. The default values are sufficient. With version 12.5, this value will be set to KMAXFD (a platform-dependent value) for each engine.
This configuration parameter determines how many rows from the source table(s) are to be bulk copied into the target table as a single batch using select into, when the target table resides in an Adaptive Server or in a DirectConnect server that supports a bulk copy interface.
If left at zero (the default), all rows are copied as a single batch. Otherwise, after the count of rows specified by this parameter has been copied to the target table, the server issues a bulk commit to the target server, causing the batch to be committed.
If a normal client-generated bulk copy operation (such as that produced by the bcp utility) is received, the client is expected to control the size of the bulk batch, and the server ignores the value of this configuration parameter.
When performing a bulk transfer of data from Adaptive Server Enterprise to another Adaptive Server Enterprise, CIS buffers rows internally, and asks the Open Client bulk library to transfer them as a block. The size of the array is controlled by a new configuration parameter cis bulk insert array size. The default is 50 rows, and the property is dynamic, allowing it to be changed without server reboot.
This configuration parameter determines the wait time in seconds for a successful Client-Library connection. By default, no timeout is provided.
This configuration parameter allows users to specify the cursor row count for cursor open and cursor fetch operations. Increasing this value means more rows will be fetched in one operation. This increases speed but requires more memory. The default is 50.
This configuration parameter allows you to specify the size of Tabular Data Stream™ (TDS) packets that are exchanged between the server and a remote server when connection is initiated.
The default packet size on most systems is 512 bytes, which is adequate for most applications. However, larger packet sizes may result in significantly improved query performance, especially when text and image or bulk data is involved.
If a packet size larger than the default is specified, and the requested server is release 10.0 or later, then the target server must be configured to allow variable-length packet sizes. Adaptive Server configuration parameters of interest in this case are:
maximum network packet size
Refer to the System Administration Guide for a complete explanation of these configuration parameters.
This global configuration parameter determines whether Component Integration Services will handle outbound RPC requests by default. When this is enabled using sp_configure “cis rpc handling” 1, all outbound RPCs are handled by Component Integration Services. When you use sp_configure “cis rpc handling” 0, the Adaptive Server site handler is used. The thread cannot override it with set cis_rpc_handling on. If the global property is disabled, a thread can enable or disable the capability, as required.
For more information on using the Adaptive Server site handler vs. using Component Integration Services to handle outbound RPCs, see “RPC handling and Component Integration Services”.