Progress DataDirect Connect for JDBC for SQL Server
An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release.
Version 6.0.0
CERTIFICATIONS
- Certified with SQL Server 2019*
Driver version 6.0.0.000249 (F000439.U000220)
- Certified with Oracle JDK 11*
Driver version 6.0.0.000062 (F000147.U000072)
- Certified with OpenJDK 11*
Driver version 6.0.0.000062 (F000147.U000072)
- Certified with OpenJDK 8 on Windows and Linux*
Driver version 6.0.0.000062 (F000147.U000072)
- Microsoft SQL Server 2017
- Microsoft Analytics Platform System 10.00
ENHANCEMENTS
- The driver has been enhanced to support inserts into IDENTITY columns for data replication. You can enable inserts into IDENTITY columns defined as NOT FOR REPLICATION using the new EnableReplicationUser connection property.*
- The driver has been enhanced to support Azure AD authentication using
Service principal users. You can configure this feature using the refreshed AuthenticationMethod property, and the new ActiveDirectoryPrincipalID and ActiveDirectoryPrincipalSecret properties.*
- The driver has been enhanced to use sp_describe_undeclared_parameters, a
SQL Server system stored procedure, to fetch parameter metadata. Using this
stored procedure, the driver can return more accurate parameter metadata for
both simple and complex queries.*
- The driver has been enhanced to support authentication using an access token.
Refer to the user's guide for more information.*
- The driver has been enhanced to support Windows Defender Credential Guard
when using Kerberos Authentication.*
- The driver has been enhanced to include timestamp in the Spy and JDBC packet
logs by default. If required, you can disable the timestamp logging by
specifying the following at connection: For Spy logs, set
spyAttributes=(log=(file)Spy.log;timestamp=no) and for JDBC packet logs,
set ddtdbg.ProtocolTraceShowTime=false.*
- Interactive SQL for JDBC (JDBCISQL) is now installed with the product. JDBCISQL is a command-line interface that supports connecting your driver to a data source, executing SQL statements and retrieving results in a terminal. This tool provides a method to quickly test your drivers in an environment that does not support GUIs.*
- The driver has been enhanced to support encrypted parameters in stored
procedures when using the Always Encrypted feature.*
- The driver has been enhanced to support the Always Encrypted feature.
Beginning with SQL Server 2016, Azure SQL and SQL Server databases support
Always Encrypted, which allows sensitive data to be stored on the server in
an encrypted state such that the data can only be decrypted by an authorized
application. The following are highlights of this enhancement:*
- The driver detects all supported native data types stored in encrypted
columns and transparently encrypts values bound to SQL parameters or
decrypts values returned in results.
- The driver supports configurable caching of column encryption keys for
improved performance.
- The driver supports using Java KeyStore and Azure Key Vault as
keystore providers.
You can enable support for Always Encrypted using the following new options:
ColumnEncryption, AEKeyCacheTTL, AEKeystoreClientSecret, AEKeystoreLocation,
AEKeystorePrincipalId, and AEKeystoreSecret. Refer to the user's guide for
more information.
Important: Always Encrypted support requires the driver to run on a Java
Virtual Machine (JVM) that is Java SE 8 or higher.
- The driver has been enhanced to transparently connect to Microsoft Azure Synapse Analytics and Microsoft Analytics Platform System data sources.
- The driver has been enhanced to support Always On Availability Groups. Introduced in SQL Server 2012, Always On Availability Groups is a replica database environment that provides a high-level of data availability, protection, and recovery.
- The driver has been enhanced to support Azure Active Directory authentication (Azure AD authentication). Azure AD authentication is an alternative to SQL Server Authentication that allows administrators to centrally manage user permissions to Azure SQL Database data stores.
- The driver has been enhanced to support Kerberos Constrained Delegation. Sometimes referred to as impersonation, Constrained Delegation allows the driver to establish a connection with credentials passed via a GSSCredential object.
CHANGED BEHAVIOR
- 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 drivers 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, including
IBM SDK (Java Edition).*
- For Kerberos authentication environments, the following changes have been implemented.
- The driver no longer sets the java.security.auth.login.config system property to force the use of the installed JDBCDriverLogin.conf file as the JAAS login configuration file. By default, the driver now uses the default JAAS login configuration file for Java, unless you specify a different location and file using the java.security.auth.login.config system property.
- The driver no longer sets the java.security.krb5.conf system property to force the use of the krb5.conf file installed with the driver jar files in the /lib directory of the product installation directory.
Version 5.1.4
CERTIFICATIONS
- Certified with Oracle JDK 11*
Driver version 5.1.4.000242 (F000381.U000186)
- Certified with OpenJDK 11*
Driver version 5.1.4.000242 (F000381.U000186)
- Certified with OpenJDK 8 on Windows and Linux*
Driver version 5.1.4.000242 (F000381.U000186)
- Microsoft SQL Server 2016*
ENHANCEMENTS
- Support for NTLMv2 has been added to the driver. You can use the AuthenticationMethod connection property to specify that the driver use NTLMv2 authentication when establishing a connection.
- The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
- Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
- Added the RegisterStatementPoolMonitorMBean connection property. Note that the
driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
You must set RegisterStatementPoolMonitorMBean to true to register the Statement Pool Monitor and manage statement pooling with standard JMX API calls.*
Version 5.1.3
CERTIFICATIONS
- Microsoft SQL Server 2014
Version 5.1.1
ENHANCEMENTS
- Added ApplicationIntent connection property, which enables you to request read-only routing and connect to read-only database replicas.
- Enhanced drivers so that transaction isolation level may only be changed before the transaction is started.
- Enhanced to throw warning when EnableBulkLoad fails
Version 5.1.0
CERTIFICATIONS
- Microsoft SQL Server 2012
- Microsoft Windows Azure SQL Database