Make the encryption Optional.  techcommunity.microsoft.com/.../3169228

Thank you, Jay, for the answer. It seems this is very technical. Is there an easy way to do it?

Yes, it was so easy. I wonder why that change is not done by Sage 300 when it creates the ODBC.

Because Microsoft's ODBC installer that Sage has to use has it on by default.

Hi Serob Jay's nailed it, and this likely provides maximum performance avoiding the encryption overhead though I wanted to add we often have to tick Trust Server Certificate instead, leaving the encryption Mandatory due to clients with a data transport security policy (particularly Government) but are yet to install a certificate on the SQL server.  I suspect Sage have it Mandatory as default to comply with certain security standards as part of their new initiative around security compliance https://www.sage.com/en-us/trust-security/security/.