Service-specific configuration parameters

The parameters that are not global can be specified for any service. However, if a service-specific keyword is not defined, the default value applies. Additional services after the primary service do not inherit service-specific parameters from the primary service. These parameters are used with “sp_configure”.

Table A-3 lists the service-specific parameters:

Table A-3: Service-specific configuration parameters

Keyword

Description

Default

autocommit

Gives transactional control in passthrough mode.

1

array_size

Specifies the number of rows retrieved with a single fetch.

50

connect_string

Defines a connection to the target Oracle database.

csp_uppercase

Assigns uppercase object names when executing catalog stored procedures.

1

date_format

Applies the syntax for inserting dates in passthrough mode.

MON DD YYYY HH:MI:SSAM

default_precision

Specifies the Sybase precision when an Oracle number datatype is defined without precision or scale.

38

default_scale

Specifies the Sybase scale when an Oracle number datatype is defined without precision or scale.

0

insert_array_size

Specifies the number of rows to batch before issuing an insert.

50

number_mode

Determines the behavior for converting Oracle data with a datatype number.

2

session_time_limit

Specifies the maximum length of time a 2pc transaction can be inactive before it is automatically aborted by the Oracle system. The unit for this time limit is in seconds.

60

timestamp_format

Specifies the timestamp_format used in passthrough mode.

MON DD YYYY HH:MI:SSAM

timestamp_ms_support

Specifies whether the timestamp_format is used.

0

timestamp_tz_format

Specifies the timestamp_format used in passthrough mode.

MON DD YYYY HH:MI:SS.FFAM TZH:TZM

traceflags

Controls the types of messages written to the log file.

triggers

For internal use only.

0

two_phase_commit

Enables the two-phase commit feature.

0