12-16-2016 06:35 AM - edited 03-01-2019 09:24 AM
We've been using the MSSql Adapter Service successfully up to SQL Server 2014; however, now with SQL Server 2016 the adapter service fails its dbversion check and no longer connects. There's no option to select 2016 in the connection configuration and upgrading to a newer version of jdbc4 hasn't seemed to work either.
Has anyone else experienced this difficulties and do any known workarounds exist?
Solved! Go to Solution.
12-17-2016 10:59 AM
Support for MSSQQL 2016 is added in Tidal 6.2.1.582. You will need the new mssqlservice.pkg file deployed on the Master to get the pull down option of choosing mssql 2016.
Build 6.2.1.582 of TESClient and MSSQLAdapter(2.2.1.582)
CSCvb80345 : MSSQL 2016 Adapter Support
Problem : Request to add to support for SQL Server 2016.
Solution : Added the neccessary code to make the MSSQL Adapter work with SQL Server 2016.
12-17-2016 10:59 AM
Support for MSSQQL 2016 is added in Tidal 6.2.1.582. You will need the new mssqlservice.pkg file deployed on the Master to get the pull down option of choosing mssql 2016.
Build 6.2.1.582 of TESClient and MSSQLAdapter(2.2.1.582)
CSCvb80345 : MSSQL 2016 Adapter Support
Problem : Request to add to support for SQL Server 2016.
Solution : Added the neccessary code to make the MSSQL Adapter work with SQL Server 2016.
12-18-2016 12:17 AM
Thanks for the answer Robert.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: