Jdbc driver sybase

Author: g | 2025-04-23

Interactive SQL and Sybase Central support two main JDBC drivers: Sybase jConnect, and the iAnywhere JDBC Driver. Both are included with Sybase IQ. By default, the Sybase Central IQ plug-in and Interactive SQL use the iAnywhere JDBC Driver. Interactive SQL and Sybase Central support two main JDBC drivers: Sybase jConnect, and the iAnywhere JDBC Driver. Both are included with Sybase IQ. By default, the Sybase Central IQ

Sybase jConnect JDBC Driver - SAP

(Optional, replication only) To use latency monitoring (rs_ticket) in a replication environment to measure latency to non-Sybase replicate databases, you must install JDBC™ drivers to enable Sybase Control Center for Replication to connect to those replicate databases. You can install JDBC drivers at any time after installing Sybase Control Center, even if the Sybase Control Center server is already running.Download the JDBC drivers for your databases. Drivers are typically available with the database server or on the database vendor’s Web site. Oracle 9i, 10g, 11g Driver – Oracle JDBC Thin Driver 11.1 for use with JDK 1.5 (ojdbc5.jar) Microsoft SQL Server 2005 and 2008 Driver – Microsoft SQL Server JDBC Driver 2.0 (sqljdbc.jar) IBM DB2 UDB 8.22, 9.1, 9.5 Driver – IBM DB2 for Unix, Linux, and Windows JDBC Driver 9 (db2jcc.jar and db2jcc_license_cu.jar) Place the drivers in: Windows – %SYBASE%\SCC-3_2\plugins\RMAP\lib UNIX – $SYBASE/SCC-3_2/plugins/RMAP/lib If Sybase Control Center is running, stop it and start it again. Disables the Client Home Directory and Client OCS Directory controls.Client Home DirectoryBrowse to the root directory of the client to be used.Client OCS DirectorySelect the OCS- directory corresponding to the client version that you want to use.Connection SettingsSQL INI FileBrowse to locate and select the specific, SQL.INI-formatted file containing server-configuration information. The file does not have to be named SQL.INI.Packet Size, Max Connections, and Client Character SetThese settings let you create a set of default parameters used in setting up connections to Sybase ASE datasources. These settings can be overridden when registering a Sybase ASE datasource. For details, see Providing Sybase ASE Connection Information When Registering Datasources.Default Driver SelectionBy default, when you register a datasource, the native driver is automatically selected as the default connection option.NOTE: For details on native driver and JDBC driver support, see the ReadMe file selecting View > Release Notes.The controls in this group let you specify one of the installed or packaged DBMS platform-specific JDBC drivers as the default connection option.Connect using JDBC instead of the Sybase Open ClientFor platforms for which a native driver is supported, this check box enables selection of a JDBC driver as the default connection option.For platforms for which no native driver is available, this check box is disabled.JDBC driver to useIf multiple JDBC drivers are available for this platform, this control lets you select the specific JDBC driver to use as the default.Assign to all disconnected DatasourcesThis control lets you assign either the native driver or the currently selected JDBC driver as the connection option for all datasources defined on the relevant DBMS platform that are currently not connected. If the Connect using JDBC instead of the Sybase Open Client setting is selected, all disconnected datasources are assigned the driver selected from the JDBC driver to use list as the connection option. Otherwise, the native driver is assigned to all disconnected datasources on this DBMS platform.Connection Options - Sybase IQThe Connection > Sybase IQ tab of the Options Editor lets you specify DBMS-specific connection options.Note: For information on opening the Options Editor, see Specifying Application Preferences and Feature Options.Note:

OpenLink Software - JDBC Drivers for Sybase

WebLogic Type 4 JDBC Drivers The following sections describe how to configure and use the BEA WebLogic Type 4 JDBC Sybase driver:Database Version SupportDriver ClassesSybase URLSybase Connection PropertiesData TypesSQL Escape SequencesIsolation LevelsUsing Scrollable CursorsLarge Object (LOB) SupportBatch Inserts and UpdatesParameter Metadata SupportAuto-Generated Keys SupportSybase JTA SupportDatabase Version SupportThe BEA WebLogic Type 4 JDBC driver for Sybase (the "Sybase driver") supports the following database versions:Sybase Adaptive Server 11.5 and 11.9Sybase Adaptive Server Enterprise 12.0, 12.5, and 12.5.1Note: XA connections are supported with the Sybase Adaptive Server Enterprise 12.0 and later versions only. XA connections are not supported on Sybase Adaptive Server 11.5 and 11.9.Driver ClassesThe driver class for the BEA WebLogic Type 4 JDBC Sybase driver is:XA: weblogic.jdbcx.sybase.SybaseDataSourceNon-XA: weblogic.jdbc.sybase.SybaseDriverUse these driver classes when configuring a JDBC data source in your WebLogic Server domain.Sybase URLTo connect to a Sybase database, use the following URL format:jdbc:bea:sybase://dbserver:portSybase Connection PropertiesTable 7-1 lists the JDBC connection properties supported by the Sybase driver, and describes each property. You can use these connection properties in a JDBC data source configuration in your WebLogic Server domain. To specify a property, use the following form in the JDBC data source configuration:property=valueNote: All connection string property names are case-insensitive. For example, Password is the same as password.Table 7-1 Sybase Connection Properties Property Description BatchPerformanceWorkaroundOPTIONAL {true | false}. Determines the method used to execute batch operations. If set to true, the native Sybase batch mechanism is used. If set to 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.See Batch Inserts and Updates. CodePageOverrideOPTIONAL 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. ConnectionRetryCountOPTIONAL The number of times the driver retries connections to a database server until a successful connection is established. Valid values are 0 and any positive integer.The default is 0. ConnectionRetryDelayOPTIONAL The number of seconds the driver waits before retrying connections to a database server when ConnectionRetryCount is set to a positive integer.The default is 3. DatabaseNameOPTIONAL The name of the database to which you want to connect. InsensitiveResultSetBufferSizeOPTIONAL {-1 | 0 | x}. Determines the amount of memory used by the driver to cache insensitive result set data. It must have one of the following values:If set to -1, the driver caches all insensitive result set data in memory. If the size of the result set exceeds available memory, an OutOfMemoryException is generated. Because the need to write result set data to disk is eliminated, the driver processes the data more efficiently.If set to 0, the driver caches all insensitive result set data in memory,. Interactive SQL and Sybase Central support two main JDBC drivers: Sybase jConnect, and the iAnywhere JDBC Driver. Both are included with Sybase IQ. By default, the Sybase Central IQ plug-in and Interactive SQL use the iAnywhere JDBC Driver.

Download JDBC Driver for Sybase IQ

Editor lets you specify DBMS-specific connection options.Note: For information on opening the Options Editor, see Specifying Application Preferences and Feature Options.Note: For more general connectivity options, see Connection Options.GroupSettingDescriptionDefault Driver SelectionBy default, when you register a datasource, the native driver is automatically selected as the default connection option.NOTE: For details on native driver and JDBC driver support, see the ReadMe file selecting View > Release Notes.The controls in this group let you specify one of the installed or packaged DBMS platform-specific JDBC drivers as the default connection option.Connect using JDBC instead of the PostgreSQL ODBC driverFor platforms for which a native driver is supported, this check box enables selection of a JDBC driver as the default connection option.For platforms for which no native driver is available, this check box is disabled.JDBC driver to useIf multiple JDBC drivers are available for this platform, this control lets you select the specific JDBC driver to use as the default.Assign to all disconnected DatasourcesThis control lets you assign either the native driver or the currently selected JDBC driver as the connection option for all datasources defined on the relevant DBMS platform that are currently not connected. If the Connect using JDBC instead of the PostgreSQL ODBC driver setting is selected, all disconnected datasources are assigned the driver selected from the JDBC driver to use list as the connection option. Otherwise, the native driver is assigned to all disconnected datasources on this DBMS platform.Connection Options - SybaseThe Connection > Sybase tab of the Options Editor lets you select an installed client other than the active/default client version for IDERA driver connections. It also lets you override default client/server settings.Note: For information on opening the Options Editor, see Specifying Application Preferences and Feature Options.Note: For more general connectivity options, see Connection Options.GroupSettingDescriptionUse Quoted IdentifiersIf you plan to use delimited identifiers, select this option.Sybase Open Client SelectionThis group of controls apply only to use of the IDERA drivers with native Sybase clients.Enable Client SelectionSelecting this check box lets you override the default/active Sybase client specified by the SYBASE, SYBASE_OCS, and/or SYBROOT environment variables. This control enables and Linux-x86-MySQL Connector/ODBC 8.0.25 MySQL 8.0.26 server MySQL JDBC driver version 8.0.26 Windows-MySQL Connector/ODBC 8.0.26 Linux-x86-MySQL Connector/ODBC 8.0.26 Oracle Server 19.10 Oracle JDBC Driver 19.10.0.0.0 Windows-Oracle Client Version 19.3.0 Linux-x86-Oracle Client Version 19.3.0 Oracle Server 19.11 Oracle JDBC Driver 19.11.0.0.0 Windows-Oracle Client Version 19.3.0 Linux-x86-Oracle Client Version 19.3.0.0 Oracle Server 19.12 Oracle JDBC Driver 19.12.0.0.0 Windows-Oracle Client Version 19.3.0 Linux-x86-Oracle Client Version 19.12.0.0 Oracle Server 21.1 Oracle JDBC Driver 21.1.0.0.0 Windows-Oracle Client Version 19.10 Linux-x86-Oracle Client Version 19.12 Oracle Server 21.3 Oracle JDBC Driver 21.1.0.0.0 Windows-Oracle Client Version 19.10 Linux-x86-Oracle Client Version 19.12 Netezza Server 7.2.1 Netezza JDBC driver 7.2.1.10 Windows-IBM Netezza ODBC driver Version 7.2.1.11 Linux-x86-IBM Netezza ODBC driver Version-7.2.1.11 SQL Server 2017 CU24 Microsoft SQL Server JDBC driver version 9.2.0 Windows-SQL Server Native Client 11 (SQLNCLI11.DLL) Windows-ODBC Driver for SQL Server 17 Linux-x86-DataDirect ODBC Driver 8.0.2 SQL Server 2019 CU10 Microsoft SQL Server JDBC driver version 9.2.0 Windows-Microsoft OLE DB Driver for SQL Server 18.6 (MSOLEDBSQL.DLL) Windows-ODBC Driver for SQL Server 17 Linux-x86-DataDirect ODBC Driver 8.0.2 SQL Server 2019 CU11 Microsoft SQL Server JDBC driver version 9.2.0 Microsoft SQL Server JDBC driver version 9.4.0 Windows-Microsoft ODBC Driver 17.05 for SQL Server Linux-x86-DataDirect Version 08.02 SQL Server 2019 CU12 Microsoft SQL Server JDBC driver version 9.2.0 Microsoft SQL Server JDBC driver version 9.4.0 Windows-Microsoft ODBC Driver 17.05 for SQL Server Linux-x86-DataDirect Version 08.02 Informix V14.10.XC5 server Informix JDBC driver version 4.50.JC4W1 Windows-Informix SDK 4.10 TC14 Linux-x86-Informix SDK 4.10 TC15 Informix V14.10.XC6 server Informix JDBC driver version 4.50.JC4W1 Windows-Informix SDK 4.10 TC14 Linux-x86-Informix SDK 4.10 TC15 Sybase ASE Server 16 SP3 SAP JConnect JDBC driver version 16.1.3 SAP JConnect JDBC driver version 20.0.0 Windows-SAP Client-Library 16.0 Linux-x86-SAP Client-Library 16.0 SP4 Sybase IQ Server 16.1 SP3 SAP JConnect JDBC driver version 16.1.3 Windows-SAP IQ ODBC driver 16.0SP11 Linux-x86-SAP IQ ODBC driver 16.0 SP11 Sybase IQ Server 16.1 SP4 SAP JConnect JDBC driver version 20.0.0 Windows-SAP IQ ODBC driver 16.0SP11 Linux-x86-SAP IQ ODBC driver 16.0 SP11 IBM Performance server/Netezza 11.2.0.0 server Netezza nzjdbc 11.2.0.0 Windows- ODBC driver 11.2.0.0 Linux-x86- ODBC driver 11.2.1.1

JDBC Driver for Sybase - CData Software

Which is defined as a hint because the driver may not always be able to satisfy the requested method.Direct—When the driver uses the Direct method, the database server sends the complete result set in a single response to the driver when responding to a query. A server-side database cursor is not created. Typically, responses are not cached by the driver. Using this method, the driver must process all the response to a query before another query is submitted. If another query is submitted (using a different statement on the same connection, for example), the driver caches the response to the first query before submitting the second query. Typically, the Direct method performs better than the Cursor method.Cursor—When the driver uses the Cursor method, a server-side database cursor is requested. The rows are retrieved from the server in blocks when returning forward-only result sets. The JDBC Statement method setFetchSize can be used to control the number of rows that are retrieved for each request. Performance tests show that the value of setFetchSize significantly impacts performance when the Cursor method is used. There is no simple rule for determining the setFetchSize value that you should use. We recommend that you experiment with different setFetchSize values to find out which value gives the best performance for your application. The Cursor method is useful for queries that produce a large amount of data, particularly if multiple open result sets are used.The default is Direct. ServerName Specifies either the IP address or the server name (if your network supports named servers) of the primary database server. For example, 122.23.15.12 or SybaseServer. User The case-insensitive user name used to connect to your Sybase database. A user name is required only if security is enabled on your database. If so, contact your system administrator to get your user name. Data TypesTable 7-2 lists the data types supported by the Sybase driver and how they are mapped to JDBC data types.Table 7-2 Sybase Data Types Sybase Database Sybase Data Type JDBC Data Type Sybase 11.5 and higher binary BINARY bit BIT char CHAR datetime TIMESTAMP decimal DECIMAL float FLOAT image LONGVARBINARY int INTEGER money DECIMAL nchar CHAR numeric NUMERIC nvarchar VARCHAR real REAL smalldatetime TIMESTAMP smallint SMALLINT smallmoney DECIMAL sysname VARCHAR text LONGVARCHAR timestamp VARBINARY tinyint TINYINT varbinary VARBINARY varchar VARCHAR Sybase 12.5 and 12.5.1 only date DATE time TIME unichar CHAR univarchar VARCHAR Note: FOR USERS OF ADAPTIVE SERVER 12.5 AND 12.5.1: The Sybase driver supports extended new limits (XNL) for character and binary columns—columns with lengths greater than 255. Refer to your Sybase documentation for more information about XNL for character and binary columns.See GetTypeInfo for more information about data types.SQL Escape SequencesSee SQL Escape Sequences for JDBC for information about the SQL escape sequences supported by the Sybase driver.Isolation LevelsThe Sybase driver supports the Read Committed, Read Uncommitted, Repeatable Read, and Serializable isolation levels. The default is Read Committed.Using Scrollable CursorsThe Sybase driver supports scroll-sensitive result sets only on result sets returned from tables created

JDBC Driver for Sybase - Collibra Marketplace

With an identity column. The Sybase driver also supports scroll-insensitive result sets and updatable result sets.Note: When the Sybase driver cannot support the requested result set type or concurrency, it automatically downgrades the cursor and generates one or more SQLWarnings with detailed information.Large Object (LOB) SupportAlthough Sybase does not define a Blob or Clob data type, the Sybase driver allows you to retrieve and update long data, specifically LONGVARBINARY and LONGVARCHAR data, using JDBC methods designed for Blobs and Clobs. When using these methods to update long data as Blobs or Clobs, the updates are made to the local copy of the data contained in the Blob or Clob object.Retrieving and updating long data using JDBC methods designed for Blobs and Clobs provides some of the same advantages as retrieving and updating Blobs and Clobs. For example, using Blobs and Clobs:Provides random access to dataAllows searching for patterns in the data, such as retrieving long data that begins with a specific character stringTo provide these advantages of Blobs and Clobs, data must be cached. Because data is cached, you will incur a performance penalty, particularly if the data is read once sequentially. This performance penalty can be severe if the size of the long data is larger than available memory.Batch Inserts and UpdatesThe Sybase driver provides the following batch mechanisms:A JDBC 3.0-compliant mechanism that uses code in the driver to execute batch operations. This is the default mechanism used by the Sybase driver.A mechanism that uses the Sybase native batch functionality. This mechanism may be faster than the standard mechanism, particularly when performance-expensive network roundtrips are an issue. Be aware that if the execution of the batch results in an error, the driver cannot determine which statement in the batch caused the error. In addition, if the batch contained a statement that called a stored procedure or executed a trigger, multiple update counts for each batch statement or parameter set are generated.To use the Sybase native batch mechanism, set the BatchPerformanceWorkaround connection property to true. For more information about specifying connection properties, see Sybase Connection Properties.Parameter Metadata SupportThe Sybase driver supports returning parameter metadata for all types of SQL statements.Auto-Generated Keys SupportThe Sybase driver supports retrieving the values of auto-generated keys. An auto-generated key returned by the Sybase driver is the value of an identity columnHow you retrieve the values of auto-generated keys depends on whether the Insert statement you are using contains parameters:When using an Insert statement that contains no parameters, the Sybase driver supports the following form of the Statement.execute and Statement.executeUpdate methods to inform the driver to return the values of auto-generated keys: Statement.execute (String sql, int autoGeneratedKeys) Statement.executeUpdate (String sql, int autoGeneratedKeys) When using an Insert statement that contains parameters, the Sybase driver supports the following form of the Connection.prepareStatement method to inform the driver to return the values of auto-generated keys:Connection.prepareStatement (String sql, int autoGeneratedKeys) The application fetches the values of generated keys from the driver using the Statement.getGeneratedKeys() method.Sybase JTA SupportBefore you can use. Interactive SQL and Sybase Central support two main JDBC drivers: Sybase jConnect, and the iAnywhere JDBC Driver. Both are included with Sybase IQ. By default, the Sybase Central IQ plug-in and Interactive SQL use the iAnywhere JDBC Driver.

CData JDBC Driver for Sybase - DbVisualizer

For more general connectivity options, see Connection Options.SettingDescriptionUse Quoted IdentifiersIf you plan to use delimited identifiers, select this option.Default Driver SelectionBy default, when you register a datasource, the native driver is automatically selected as the default connection option.NOTE: For details on native driver and JDBC driver support, see the ReadMe file selecting View > Release Notes.The controls in this group let you specify one of the installed or packaged DBMS platform-specific JDBC drivers as the default connection option.Connect using JDBC instead of the Sybase IQ ODBC DriverFor platforms for which a native driver is supported, this check box enables selection of a JDBC driver as the default connection option.For platforms for which no native driver is available, this check box is disabled.JDBC driver to useIf multiple JDBC drivers are available for this platform, this control lets you select the specific JDBC driver to use as the default.Assign to all disconnected DatasourcesThis control lets you assign either the native driver or the currently selected JDBC driver as the connection option for all datasources defined on the relevant DBMS platform that are currently not connected. If the Connect using JDBC instead of the Sybase IQ ODBC Driver setting is selected, all disconnected datasources are assigned the driver selected from the JDBC driver to use list as the connection option. Otherwise, the native driver is assigned to all disconnected datasources on this DBMS platform.Connection Options - SQL ServerThe Connection > SQL Server tab of the Options Editor lets you specify DBMS-specific connection options.Note: For information on opening the Options Editor, see Specifying Application Preferences and Feature Options.Note: For more general connectivity options, see Connection Options.SettingDescriptionSQL Server Native Client SelectionThese controls let you specify a default native driver.NOTE: For details on native driver and JDBC driver support, see the ReadMe file selecting View > Release Notes.Enable Client SelectionWhere multiple native drivers are supported, this check box enables selection of a native client to use as the default option.ClientsSelect the native client to be used as default.Use Quoted IdentifiersIf you plan to use delimited identifiers, select this option.Connection SettingsPacket SizeThis control lets you specify a