CommLinks ShMem connection parameter (use shared memory) replaces NONE Use CommLinks=ShMem to explicitly specify shared memory. As in previous versions of Sybase IQ, connections that do not specify a CommLinks connection parameter always attempt to connect over shared memory.
Connection errors abort process (behavior change) Previously, connection protocols listed in the CommLinks connection parameter were attempted one by one until a connection occurred. Now, if a connection error occurs during the process, it aborts the connection process immediately, regardless of whether or not all the listed protocols were tried.
SharedMemory tried first (behavior change) Previously, the ports specified in the LINKS= connection parameter were tried in the order in which they were specified. Now, if the SharedMemory (shmem) port is specified, it is tried first, followed by the other ports specified in the order in which they appear.
For more information, see “CommLinks connection parameter [Links]” in Chapter 4, “Connection and Communication Parameters” of the Sybase IQ System Administration Guide.
Default packet size change (behavior change) The default packet size for client/server communications has been changed from 1024 bytes to 1460 bytes.
For more information on packet size, see the -p server option in “Starting the database server” in the Sybase IQ Utility Guide, and “CommBufferSize connection parameter [CBSize]” in Sybase IQ System Administration Guide.
PrefetchBuffer connection parameter (behavior change) The default value has been increased from 32 to 64 (KB). This connection parameter lets you specify the maximum amount of memory for storing prefetched rows.
For more information, see “PrefetchBuffer connection parameter [PBUF]” in Sybase IQ System Administration Guide.
The network server supports the LocalOnly communication parameter [LOCAL] You can use the LocalOnly communication parameter [LOCAL] with the server. Running a server with the LocalOnly communication parameter set to YES allows the network server to run as a personal server without experiencing connection or CPU limits.
For more information, see “LocalOnly communication parameter [LOCAL]” in Sybase IQ System Administration Guide.
Database server registers with LDAP The database server can now register itself with an LDAP server, so that clients and the Locate Utility [DBLOCATE] can query the LDAP server to find it. This allows clients running over a WAN or through a firewall to find servers without specifying the IP address to find such servers. LDAP is only used with TCP/IP, and only on network servers.
For more information, see “LDAP communication parameter [LDAP]” in Sybase IQ System Administration Guide.
New communication parameters can improve network responsiveness The LazyClose and PrefetchOnOpen network communication parameters can improve performance on networks with poor latency or with applications that process many requests.
For information about these parameters, see “LazyClose connection parameter [LCLOSE]” and “PreFetchOnOpen communication parameter” in Sybase IQ System Administration Guide
Improved handling of a large number of connections (behavior change) The liveness timeout value now increases automatically when there are more than 200 connections in an effort to better handle a large number of connections.
For more information, see “Starting the database server” in Sybase IQ Utility Guide and “LivenessTimeout connection parameter [LTO]” in Sybase IQ System Administration Guide.
New LocalOnly connection parameter controls broadcasts You can use the LocalOnly connection parameter to connect only to a server on the local machine, if one exists. Setting LocalOnly=YES uses the regular broadcast mechanism, except that broadcast responses from servers on other machines are ignored.
For more information, see “LocalOnly communication parameter [LOCAL]” in Sybase IQ System Administration Guide.
Improved buffer size negotiation Buffer sizes can now be specified separately for both the client and the server. For more information, see “CommBufferSize connection parameter [CBSize]” in Sybase IQ System Administration Guide.
Communication compression A new type of communication compression can lead to improved performance if you are transferring data across networks with limited bandwidth, including some wireless networks, some modems, serial links and some WANs.
For more information, see the -pc and -pt server options in Chapter 5, “The Database Server,” and the COMP and COMPTH connection parameters, in Chapter 3, “Client/Server Communications, in Adaptive Server Anywhere Database Administration Guide.
DEBUG connection parameter no longer supported (behavior
change) The DEBUG connection parameter has been deprecated. You can
still use LOG parameter to create a log file containing the debug
information. As of version 12.6, LOG=filename does
what DEBUG=YES;LOG=filename used
to do.
For more information, see “LogFile connection parameter [LOG]” in Sybase IQ System Administration Guide.
UseUDP communication parameter no longer supported (behavior change) On the server side, you can specify DoBroadcast=NO. On the client side, you can specify the ClientPort communication parameter. For more information, see “DoBroadcast parameter [DBROAD]” and “ClientPort parameter [CPort]” in Sybase IQ System Administration Guide.
Port connection property removed (behavior change) The port connection property has been removed. Note that this is the connection property, not the port connection parameter.
