Skip to main content

Changelog

Updates, changes, and improvements at Retool.

Refer to the stable and edge release notes for detailed information about self-hosted releases.

89 posts tagged with "Self-hosted"

View All Tags

Deprecation of Microsoft SQL integration versions 1.0 and 2.0

Retool is deprecating versions 1.0 and 2.0 of the Microsoft SQL integration. Organizations with Microsoft SQL resources still using these versions must update their resource configuration to use version 3.0.

This deprecation will first take effect on cloud instances on August 24, 2026. It will then take effect in the next edge and stable releases that follow.

Version 3.0 has been available since February 2, 2026 for cloud instances and the 3.334 stable release. If you haven't intentionally created a resource on an older integration version, your resource is likely already on version 3.0 and requires no changes.

To upgrade an existing resource, open its settings from the Resources page, change Connector version to Version 3.0, and save your changes.

Versions 1.0 and 2.0 will be removed entirely from cloud instances in Q4 2026, followed by the subsequent edge and stable releases. After that, apps, workflows, and queries that depend on Microsoft SQL resources still using version 1.0 or 2.0 will stop working.

Microsoft SQL Server (Windows Authentication): unsupported ODBC connection params are now rejected

Retool now blocks Microsoft SQL Server resources that use Windows Authentication with custom ODBC connection parameters outside an approved allowlist. Previously, unsupported parameters were logged as warnings but still applied. They now cause resource setup to fail.

Who is affected

Self-hosted deployments using Microsoft SQL Server resources with Connect using Windows Auth enabled and one or more custom entries in Connection options (or equivalent resource JSON) whose keys are not on the allowlist. Windows Authentication is not available on Retool Cloud.

How to check if you are affected before upgrading

Search your Retool deployment logs (dbconnector / backend) for this exact string from the prior log-only release:

MSSQL Windows Auth ODBC connection string parameter not on allowlist

Each matching log line includes the parameter key (parameterKey in structured logs). Resources that logged this message will fail to connect or save after upgrading until those parameters are removed or replaced.

What you will see after upgrading

Resource setup or test connection fails with an error like:

Unsupported MSSQL ODBC connection string parameter "<key>". Only a fixed set of ODBC attributes may be supplied via connection params.

Remediation

  1. Open each affected MSSQL Windows Auth resource.
  2. Remove unsupported keys from paramsFromConnectionString.
  3. Use Retool's built-in resource fields where possible. For example, use SSL/TLS for encryption and certificate verification.
  4. If you need an ODBC attribute that is not listed below, contact Retool Support before upgrading.

Allowed paramsFromConnectionString keys

ODBC attributeAlternate spellings accepted
APPapp
ApplicationIntentapplicationintent
ColumnEncryptioncolumnencryption
ConnectRetryCountconnectretrycount
ConnectRetryIntervalconnectretryinterval
Connect TimeoutConnectTimeout, connecttimeout
Failover_Partnerfailoverpartner
FailoverPartnerSPNfailoverpartnerspn
HostnameInCertificatehostnameincertificate
IpAddressPreferenceipaddresspreference
KeepAlivekeepalive
Languagelanguage
LoginTimeoutlogintimeout
MARS_Connectionmarsconnection
MultiSubnetFailovermultisubnetfailover
Packet SizePacketSize, packetsize
QueryLog_Onquerylogon
QueryLogTimequerylogtime
Regionalregional
ServerSPNserverspn, Server_SPN
Workstation IDWorkstationID, workstationid
WSIDwsid

Security-sensitive attributes (Driver, Encrypt, Trusted_Connection, credentials, Server, Database, and similar) are set by Retool and cannot be supplied via connection params.

Common parameters that are blocked

  • Encryption and certificate trust settings such as Encrypt and TrustServerCertificate — use the resource SSL/TLS settings instead.
  • LoginRetryCount / LoginRetryInterval — use ConnectRetryCount / ConnectRetryInterval.
  • Credential keys such as Uid, Pwd, User, or Password.
  • Keys containing ; or crafted to inject additional ODBC attributes.