skip to main content
Welcome to the Progress DataDirect for ODBC for Salesforce™ Driver : What's New in this Release?
  

Try DataDirect Drivers Now

What's New in this Release?

Changes Since 8.0.0

*Driver Enhancements
*yes, no, on and Off have been added as valid values for the connection options that accept boolean values.
*The driver has been enhanced to support OAuth 2.0 authentication. See Configuring OAuth 2.0 authentication for details.
*Changed Behavior
*The driver has been updated to require a Java Virtual Machine (JVM) that is Java SE 8 or higher, including Oracle JDK, OpenJDK, and IBM SDK (Java) distributions. See Driver Requirements for more details on JVM.
Java SE 7 has reached the end of its product life cycle and will no longer receive generally available security updates. As a result, the driver will no longer support JVMs that are version Java SE 7 or earlier. Support for distributed versions of Java SE 7 and earlier will also end.
*The configuration options have been deprecated. However, the driver will continue to support them until the next major release of the driver.
*The precision for the Integer data type has been changed from 10 to 9.
*The NUM_PREC_RADIX value for the Double data type has been changed from 10 to 2.
*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)
*Windows XP (all versions)
*Windows Server 2003 (all versions)

Changes For 8.0.0

*Driver Enhancements
*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. See Summary of Options for Using Bulk API with SQL Statements for details.
*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. See WSPoolSize for details.
*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. See Refresh Map (EXT) for details.
*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). See SQL Engine Mode for details.
*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. Refer to Windows quick start for details.
*The driver and Driver Manager have been enhanced to support UTF-8 encoding in the odbc.ini and odbcinst.ini files. See Character Encoding in the odbc.ini and odbcinst.ini Files for details.
*Changed Behavior
*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. See Driver Requirements for more details on JVM.
*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. See also Supported SQL Statements and Extensions.
*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. See Data Types details.
*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. See Schema Map for details.
*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. See Create Map for details.
*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. See User Name for details.
*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. See Schema Map for details.
*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. See Enable Bulk Load for details.
*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. See Statement Call Limit for details.
*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. See AuditColumns (Config Option) for details.
*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. See CustomSuffix (Config Option) for details.
*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. See MapSystemColumnNames (Config Option) for details.
*The short attribute name for the Config Options connection option has changed from CO to CFGO. See Config Options for details.
*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.