Overview
"Do we need to update our ODBC driver to be able to use SQL Server 2022?" was the initial inquiry. After updating to ODBC Driver 18, operations in Pivotal Administration Console failed. The issue was resolved by ensuring SQL Server TLS 1.2 configuration and using SQL Server Native Client 10.0 for compatibility, as newer drivers may cause issues with Pivotal 6.6.5.3.
Information
Issue: Compatibility issues with Pivotal 6.6.5.3 after updating ODBC driver for SQL Server 2022.
Error Message: Operations in Pivotal Administration Console fail post-ODBC driver update.
Cause: Incompatibility between newer ODBC drivers and Pivotal's data access layer.
Resolution Steps:
-
Verify SQL Server TLS 1.2 Configuration:
- Ensure your SQL Server is configured to use TLS 1.2.
- Refer to the article: "Enabling TLS 1.2 for SQL Server connection with ODBC in Pivotal Systems".
-
Revert to SQL Server Native Client 10.0:
- Change ODBC connections to use SQL Server Native Client 10.0.
- This driver is often the most reliable for Pivotal 6.x.
-
Verify Resolution:
- Test operations in Pivotal Administration Console.
- Confirm that system restore and other functions work as expected.
Note: If issues persist, provide updated logs and sysmgr/clone/restore logs from the Syncstream folder for further analysis.
Frequently Asked Questions
- How do I know if I need to update my ODBC driver for SQL Server 2022?
- If you are using SQL Server 2022 with Pivotal 6.6.5.3, ensure your ODBC driver is compatible. However, SQL Server Native Client 10.0 is recommended for compatibility.
- What should I do if operations fail after updating the ODBC driver?
- Verify your SQL Server's TLS 1.2 configuration and revert to using SQL Server Native Client 10.0 for ODBC connections.
- Why is SQL Server Native Client 10.0 recommended?
- It is often the most reliable driver for Pivotal 6.x, as newer ODBC drivers may not be fully compatible with Pivotal's data access layer.
Priyanka Bhotika
Comments