In this article

What is happening?

We are updating the JDBC driver for SQL Server that is bundled with the SQL Server Snap Pack.

There are some changes in how the JDBC driver connects to the SQL Server instances that might require changes in your SQL Server account configuration. To minimize the impact on production pipelines, this update is being rolled out in a way that allows impacted customers to take updates gradually and within a timeframe that works for them.

This document explains everything you need to know, and what action you need to take.

Why is this change being made?

This change is necessary to keep the libraries in the SQL Server Snap current. Keeping dependencies in our Snap Packs current is important to reduce security vulnerabilities and to allow customers to leverage features that are only available with the latest dependency versions.

What is the timeline of delivery?

Currently, the SQL JDBC driver upgrade can be selected in any Org by setting the SQL Server Snap Pack to 433patches21386 or 433patches21535.

With the July 2023 release, the JDBC driver upgrade for SQL Server Snap Pack will be set to the latest distribution.

With the August 2023 release, the upgrade will be available on both the stable and latest releases across all Orgs as they are updated to the August 2023 Snaplex version.

Will I be impacted?

You will be impacted if all of the following are true:

• You are using the SQL Server Snap Pack

• You do not define a JDBC driver JAR file

  • If you are not sure, refer to What JDBC driver am I using?

• Your SQL Server instance certificate is not signed through a trusted certificate authority

What JDBC driver am I using?

If you do not specify a value in the JDBC Driver field, you are using the default driver of the Snap Pack. This means you are probably impacted by the changes.

Open

If you renamed the JAR file to remove the version number, you need to download and unzip the JAR file to look at the manifest to determine its version. (For example, the screenshot above did not remove the 10.2.0 version number.)

What do I need to change?

Typically, SQL Server SSL certificates are not signed by a Trusted Certificate Authority (CA). As a result, your Snaplex will not trust the certificate that SQL Server uses for connection. If this is the case, you must add the trustServerCertificate URL connection property set to true in the Url properties field (as s