See “Using Connection Failover” for a discussion of connection failover and information about other connection string options that you can set for this feature.where string is the name of the application.Determines how the data provider optimizes batch processing during update operations. The BatchUpdateSize property must be set to an integer greater than 1 (see “SybaseDataAdapter Class” for more information).NOTE: Setting this option is useful only when the SybaseDataAdapter UpdateBatchSize property is enabled (see “SybaseDataAdapter Class”).where string is the host name of the client machine.Determines whether the data provider clones the existing connection if another active result set is not currently possible on the existing Sybase connection and the application requires one. This connection string option can affect performance. See “Performance Considerations” for more information.0 | xwhere x is a positive integer from 1 to 65535.If set to x, the data provider attempts to connect the specified number of times. If a connection is not established during the retry attempts, the data provider returns an error that is generated by the last server to which it attempted to connect.0 | xwhere x is a positive integer from 1 to 65535.If set to x, the data provider waits the specified number of seconds between connection retry attempts.0 | xwhere x is a positive integer greater than 1.where string is the name of a database.0 | xWhere x is a positive integer 1 or higher.If set to x, tracing is enabled.When set to True and Enlist is set to True, distributed transactions are supported and calls to Connection.EnlistTransaction function normally. See “Performance Considerations” for information about using distributed transactions.NOTE: When set to False and Enlist is set to True, the data provider returns an error.See “Performance Considerations” for information about configuring this option for optimal performance.This connection string option can affect performance for the ADO.NET data provider. See “Performance Considerations” for more information.NOTE: This option is ignored unless the Authentication Method connection string option is set to Kerberos.An empty string | path_to_GSS_client_librarywhere string is a valid host name or IP address.If your network supports named servers, you can specify a server name such as Sybaseserver. Or, you can specify an IP address in IPv4 or IPv6 format or a combination of both. See “Using IP Addresses” for information about using IP addresses.empty string | host_name0 or xwhere x is any positive integerwhere command is a Sybase command.C:\install_dir\DDTek.lic0 | xwhere x is a positive integer from 1 to 65535.See “Removing Connections from a Pool” for a discussion of connection lifetimes.If set to True, the data provider attempts to connect to the database servers in random order. See “Client Load Balancing” for more information about load balancing.NOTE: This option has no effect unless alternate servers are defined for the “Alternate Servers” connection string option.The Load Balancing connection string option is an optional setting that you can use in conjunction with connection failover. See “Using Connection Failover” for a discussion of connection failover and for information about other connection options that you can set for this feature.See “Creating a Connection Pool” for more information.See “Creating a Connection Pool” for more information.0 | xwhere x is a positive integer greater than 1.This connection string option can affect performance. See “Performance Considerations” for more information.See “Removing Connections from a Pool” for a discussion of connection lifetimes.0 | xwhere x is a positive integer from 1 to 65535.This connection string option can affect performance. See “Performance Considerations” for more information.-1 | 0 | xwhere x is a positive integer from 1 to 65024.NOTE: When the BindByName property of the SybaseCommand class is set to True and this connection string option is defined as BindByName or BindByOrdinal, the value defined in the connection string is overridden for the lifetime of the SQLServerCommand Class.where string is a valid password.If set to True, connection pooling is enabled. See “Using Connection Pooling” for a discussion of connection pooling.where port is the port number.where string is a value that identifies the Client Product Version/ID on the server.See Table B-4 for a list of the names and hexadecimal values you can specify to increase the amount of database metadata returned.
Table B-4. Sybase Column Collections Schema Option=ShowProcedureDefinitions, ShowViewDefinitions or Schema Options=0x60.0x10 or ShowParameterDirectionsThis connection string option can affect performance. See “Performance Considerations” for more information.If set to Direct, Select statements are issued without using server-side database cursors. Direct can be used with multiple open statements and manual transactions. However, if the statement contains a result set larger than the value set in the Fetch Buffer Size option, the connection may have only one active result set. We recommend that you use the default unless you need database cursors.where string is the name of the section in the Interfaces file that contains the network connection information.where servicePrincipalName is the service principal name of the Sybase server to be connected to a realm, and realm is the Kerberos realm to which the Sybase server belongs. If no realm is specified, the default Kerberos realm is used.NOTE: If the Authentication Method connection string option is not set to Kerberos, the value of the Service Principal Name option is ignored.servicePrincipalName | servicePrincipalName@realmSpecifies the statement caching mode for the lifetime of the connection. See “Using Statement Caching” for more information.This connection string option can affect performance. See “Performance Considerations” for more information.This connection string option can affect performance. See “Performance Considerations” for more information.If set to True, the overall performance of the data provider is better. However, locking problems may occur with multiple connections within the same distributed transaction. See “Performance Considerations” for more information.where string is a valid user name.