You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For compatibility with MS ODBC Driver 18, the settings Encrypt and TrustServerCertificate are now always added to the connection string.
These are configured with the keys encrypt and trust_cert in your profile.
In previous versions, these settings were only added if they were set to True.
The new version of the MS ODBC Driver sets Encrypt to True by default.
The adapter is following this change and also defaults to True for Encrypt.
The default value for TrustServerConnection remains False as it would be a security risk otherwise.
This means that connections made with this version of the adapter will now have Encrypt=Yes and TrustServerCertificate=No set if you are using the default settings.
You should change the settings encrypt or trust_cert to accommodate for your use case.
This behaviour might still change in the final release of 1.2.0 based on feedback gathered during the beta phase.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Possibly breaking change: connection encryption
For compatibility with MS ODBC Driver 18, the settings
Encrypt
andTrustServerCertificate
are now always added to the connection string.These are configured with the keys
encrypt
andtrust_cert
in your profile.In previous versions, these settings were only added if they were set to
True
.The new version of the MS ODBC Driver sets
Encrypt
toTrue
by default.The adapter is following this change and also defaults to
True
forEncrypt
.The default value for
TrustServerConnection
remainsFalse
as it would be a security risk otherwise.This means that connections made with this version of the adapter will now have
Encrypt=Yes
andTrustServerCertificate=No
set if you are using the default settings.You should change the settings
encrypt
ortrust_cert
to accommodate for your use case.This behaviour might still change in the final release of 1.2.0 based on feedback gathered during the beta phase.
Features
retries
setting introduced in coretype_*
macrosbool_or
listagg
will only work in SQL Server 2017 or newer or the cloud versions. Thelimit_num
option is unsupported.DISTINCT
cannot be used in the measure.Fixes
TIMESTAMP
would be used as data type instead ofDATETIMEOFFSET
, fixed thatChores
Outstanding work for official release
This discussion was created from the release v1.2.0b2.
Beta Was this translation helpful? Give feedback.
All reactions