Progress Sonic ESB Configuration and Management Guide

Chapter 6: Driver Connection Properties and Data Types by Database Brand
Table 20. Connection Properties for the Sybase Driver (continued)
Property Description
BatchPerformanceWorkaround
OPTIONAL
CodePageOverride
OPTIONAL
For example:
jdbc:progress:sybase://server1:4100;
DatabaseName=TEST;AlternateServers=(server2:4100;
DatabaseName=TEST2,server3:4100;DatabaseName=TEST3)
contains alternate server entries for server2 and server3. The alternate
server entries contain the optional DatabaseName property.
Other properties are:
● ConnectionRetryCount — Controls the number of times the driver
retries the list of servers (primary and alternate) while attempting to
establish a connection.
● ConnectionRetryDelay — Sets the wait interval, in seconds, between
retry attempts.
● LoadBalancing — Controls the order in which the driver sequences
through the list of servers (primary and alternate) while attempting
to establish a connection.
See “Specifying Primary and Alternate Servers” on page 135 for more
information about specifying connection information for primary and
alternate servers
{true | false}
Determines the method used to execute batch operations:
● true — The native Sybase batch mechanism is used.
● false — The JDBC 3.0-compliant batch mechanism is used.
In most cases, using the native Sybase batch functionality provides
significantly better performance, but the driver may not always be able to
return update counts for the batch.
The default is false.
Specifies the code page the driver uses when converting character data.
The specified code page overrides the default database code page. All
character data retrieved from or written to the database is converted using
the specified code page. The value must be a string containing the name
of a valid code page supported by your Java Virtual Machine, for
example, CodePageOverride=CP950.
205 Progress Sonic ESB Configuration and Management Guide 8.5