MACROMEDIA COLDFUSION 5-ADVANCED ADMINISTRATION, Manual

Page: 50 / 372

32 Chapter 1 Advanced Data Source Management
Connecting to Sybase Databases
On Windows and UNIX, ColdFusion lets you access Sybase databases using ODBC
and native drivers. ColdFusion 5 supports Sybase 11 and later.
If you install ColdFusion on a Windows server, you can configure a Sybase database
as a ColdFusion data source using ODBC, OLE DB, or a native driver. For information
about using OLE DB with ColdFusion data sources, see “About OLE DB” on page 4.
ODBC: MERANT Sybase ASE Driver options
The following table describes ColdFusion options for the MERANT Sybase ASE
ODBC driver. You set these options when you configure a ColdFusion data source.
Option Description
Data Source Name A name for your ODBC data source.
Description Descriptive information about the data source.
Database Name The name of the database to which you want to connect.
Server Name The name of the server containing the Sybase tables that you
want to access. If not supplied, the initial default is the server
name in the DSQUERY environment variable. On UNIX, the
name of a server from your $SYBASE/interfaces file.
Server Port The port number that the Sybase server monitors for
requests. The default value is 5000.
Network Library
(Windows only) The name of the network library. This specifies which network
protocol to use (Winsock or NamedPipes). The default is
Winsock. This option has no effect on UNIX; on UNIX, TCP/
IP is used.
Performance Row Limit (Fetch Array Size on Windows) The number of
rows the driver retrieves from the server for a fetch. Selecting
this option can increase performance by reducing network
traffic.
Create stored procedures (UNIX only) Determines
whether stored procedures are created on the server for
every call to SQLPrepare.
When enabled, stored procedures are created for every call
to SQLPrepare. This setting can result in bad performance
when processing static statements.
When disabled, the driver does not create stored procedures.
Disable database cursors for Select statements
Determines whether database cursors are used for Select
statements. In some cases performance degradation can
occur when performing large numbers of sequential Select
statements because of the amount of overhead associated
with creating database cursors.