Any communications between a client application and a database server require a communications protocol. Sybase IQ supports a set of communications protocols for communications across networks and for same-machine communications.
The database server supports the following protocols:
Shared memory is used for same-machine communications, and is loaded by default.
TCP/IP is supported on all platforms.
Named pipes is supported on Windows 2000/2003/XP only. Named Pipes is provided for same machine communications to and from Windows client applications using ODBC or Embedded SQL, but is not generally recommended for this purpose. Named pipes is not used for network communications.
By default, the database server starts up all available protocols. You can limit the protocols available to a database server by using the –x command-line switch. At the client side, many of the same options can be controlled using the CommLinks connection parameter.
The following command starts a server using the TCP/IP protocol:
start_iq -x "tcpip" -n myserver
The quotes are not strictly required in this example, but are needed if there are spaces in any of the arguments to -x. If you omit this switch and you are using TCP/IP, or if you do not specify a port number, the default port 2638 is used.
You can add parameters to tune the behavior of the server for each protocol. For example, the following command line instructs the server to use two network cards, one with a specified port number. This command must be entered all on one line, even though it appears on multiple lines here.
start_iq -x "tcpip(MyIP=192.75.209.12:2367,192.75.209.32)" path\iqdemo.db
For detailed descriptions of network communications parameters that can serve as part of the -x switch, see “Network communications parameters”.
