Progress DataDirect for ODBC for Salesforce Driver
An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release
- Certified with OpenJDK 11
- Certified with OpenJDK 8
- Certified with Java SE 11
- Certified with Red Hat Enterprise 7.3
- Certified with Salesforce API Version 38
- Certified with Windows Server 2016
- Certified with Debian Linux 7.11, 8.5
- Certified with Ubuntu Linux 14.04, 16.04
- The driver has been enhanced to support the Salesforce Bulk API, including PK chunking, for bulk fetch operations. This functionality can be enabled and configured with the Enable Bulk Fetch, Bulk Fetch Threshold, Enable Primary Key Chunking, and PK Chunk Size connection options.
- The driver has been enhanced to support multiple simultaneous sessions. This allows the driver to scale performance by distributing the workload across multiple sessions. The number of active sessions should not exceed the number permitted by your Salesforce account and can be limited by the setting of the new WSPoolSize connection option.
- The following Refresh Map SQL extension has been added to the driver. REFRESH MAP discovers native objects that have been added to the native data store since connection or since the last refresh and maps the objects into your relational view of native data. It also incorporates any configuration changes made to your relational view by reloading the schema map and associated files.
- The SQL Engine Mode connection option now supports Auto mode. When this setting is enabled, the driver automatically determines whether the SQL engine runs in server or direct mode based on availability. In addition, the default value for the SQL Engine Mode connection option on Windows has been updated to 0 (Auto).
- The driver is now compiled using Visual Studio 2015 for improved security.
- The driver includes a new Tableau data source file (Windows only) that provides improved functionality when accessing your Salesforce data with Tableau.
- The driver and Driver Manager have been enhanced to support UTF-8 encoding in the odbc.ini and odbcinst.ini files.
The following Windows platforms have reached the end of their product lifecycle
and are no longer supported by the driver*:
- Windows 8.0 (versions 8.1 and higher are still supported)
- Windows Vista (all versions)
- Support for HP-UX PA-RISC 32-bit, Oracle Solaris SPARC 32-bit, and Oracle Solaris x86 32-bit platforms has been depricated.
- Support for Windows XP and Windows Server 2003 has been deprecated.
- The Salesforce driver has been updated to require a JVM that is version Java SE 7 or higher. This change has been implemented to remain compliant with Salesforce security standards.
- In addition to the information listed here, refer to the compatability FAQ for guidance on upgrading from the Progress DataDirect for ODBC for Salesforce 7.1 driver to the 8.0 driver.
- The driver’s SQL engine was upgraded for this release. Consequently, there are differences in how the driver handles some SQL queries. Refer to this SQL engine upgrade document for details.
- The 8.0 driver pushes queries to Salesforce whenever possible. Queries that cannot be pushed to Salesforce with the 8.0 driver may be slower than comparable queries made with earlier versions of the driver because data may be paged to disk while completing an operation. If you experience slow performance, please contact Technical Support. Our team will quickly address any performance issues you encounter.
- Bulk load operations are no longer restricted to 10,000 rows for evaluation installations of the driver.
- The native CURRENCY and PERCENTAGE data types now map to the DECIMAL JDBC data type. In earlier releases, these data types mapped to the DOUBLE data type.
- The Database connection option has been replaced by the new Schema Map option. Similar to Database, Schema Map is used to specify the name and location of the configuration file where the relational map of native data is written; however, there are changes to the file name format and default behavior. The Database attribute will continue to be supported for this release, but it will be deprecated in subsequent versions of the product.
- The Create Database connection option has been replaced by the new Create Map option. The CreateDB attribute will continue to be supported for this release, but it will be deprecated in subsequent versions of the product.
- The Logon Domain connection option has been deprecated. As a result, the User Name option has been updated to accept the user name and domain.
- The Refresh Dirty Cache option has been deprecated. Now, for every fetch operation, the driver refreshes the cached object to pick up changes made to tables and rows.
- The Server DB Directory connection option has been deprecated. To specify the location of database files, use the Schema Map connection option.
- The default value for the Server Port Number connection option has been updated:
- For the 32-bit driver, the default is 19938.
- For the 64-bit driver, the default is 19937.
- The default value for the JVM Arguments connection option has been updated:
- For the 32-bit driver when the SQL Engine Mode connection option is set to 2 (Direct): -Xmx256m
- For all other configurations: -Xmx1024m
- The default value of the Enable Bulk Load connection option has been updated to 1 (enabled). By default, the bulk load protocol is used for inserts, updates, and deletes when the size of the operation exceeds the threshold determined by the Bulk Load Threshold option.
- The default value for the Statement Call Limit connection option has been updated to 100. By default, the driver can make a maximum of 100 Web service calls when executing any single SQL statement or metadata query.
- The default value for the AuditColumns config option has been updated to All (AuditColumns=All). By default, the driver includes the all of the audit columns and the master record id column in its table definitions.
- The default value for the CustomSuffix config option has been updated to Include (CustomSuffix=Include). By default, the driver includes the "__c" suffix table and column names when mapping the remote data model to the relational data model.
- The default value for the MapSystemColumnNames config option has been updated to 0 (MapSystemColumnNames=0). By default, the driver does not change the names of the Salesforce system columns when mapping them to the relational model.
- The short attribute name for the Config Options connection option has changed from CO to CFGO.
- The Security tab has been removed from the setup dialog. As a result:
- The Security Token connection option has been moved to the General tab.
- The User Name connection option has been moved to the General tab.
- Certified with Windows 10
- Certified with Red Hat Enterprise 7.1
- Certified with CentOS Linux 7.1
- Certified with Oracle Linux 7.1
- Certified with SUSE Enterprise Server 12
- Certified with Salesforce API Version 38* (driver version 07.16.0233 (B0362, U0241))
- Certified with Salesforce API Version 34, in builds 7.15.0183 and higher
- Certified with Salesforce API Version 33, in builds 7.12.0169 and higher
- The Salesforce driver has been updated to require a JVM that is version Java SE 7 or higher. This change is being implemented to comply with recent revisions to Salesforce security standards. For more information, refer to the readme in the product installation directory and the Salesforce announcement.
- Certified with Red Hat Enterprise 7.0
- Certified with CentOS Linux 7.0
- Certified with Oracle Linux 7.0
- Certified with Windows 8.1
- Certified with Salesforce API Version 29, in builds 7.12.0083 and higher
- Certified with CentOS Linux 4.x, 5.x, and 6.x
- Certified with Oracle Linux 4.x, 5.x, and 6.x
- Certified with Salesforce API Version 28, in builds 7.12.0065 and higher
- Certified with Oracle Solaris 11.1
- Certified with Salesforce API Version 27, in builds 7.10.0038 and higher
- Certified with Red Hat 6.3
- Certified with Windows 8 and Windows Server 2012
- Certified with Salesforce API Version 26
- The RefreshSchema option determines whether the driver automatically refreshes the remote object mapping and other information contained in a remote schema the first time a user connects to the specified embedded database.
- The KeywordConflictSuffix keyword=value pair specifies a string of up to
five alphanumeric characters that the driver appends to any object or field name that conflicts with a SQL engine keyword. For example, if you specify KeywordConflictSuffix=TAB, then the driver maps the Case object in Salesforce to CASETAB.