You are here
Using SSL with MS SQL
To ensure stable connectivity with Microsoft SQL Server, it’s important to match the correct JDBC driver version with your version of MyConnection Server (MCS).
Due to enforced SSL encryption defaults in JDBC 9.2 and later, and because MCS versions 11.3f and below do not expose connection string encryption options, using a driver newer than version 8.4 may result in SSL errors or connection failures unless your SQL Server is correctly configured with a trusted TLS certificate.
For instructions on how to install a SQL driver click here.
| JDBC Driver Version | SSL Default Behavior | MCS 11.3f and Below | MCS 11.3g and Later | Notes |
|---|---|---|---|---|
| 8.4 and below | encrypt=false (No SSL) |
✅ Supported | ✅ Supported | Recommended for environments without a trusted SQL Server certificate. |
| 9.2 to 12.x | encrypt=true (SSL required) |
❌ Not Supported | ✅ Supported | Requires trusted TLS cert. MCS 11.3f and below cannot configure encrypt. |
| Future Drivers | encrypt=true (likely) |
❌ Not Supported | ✅ Supported | Always check release notes. Use latest MCS to control SSL settings. |
Beginning with JDBC 9.2, Microsoft changed the default encrypt setting to true, meaning the driver will enforce SSL encryption even if not explicitly requested. Without a valid and trusted TLS certificate, this will cause the connection to fail. MCS versions 11.3f and earlier do not provide an interface to control this behavior, so only JDBC 8.4 or earlier should be used unless your SQL Server is fully configured for TLS.