The idea is:
Allow the SQL Server credential to support additional connection parameters for MultiSubnetFailover and ApplicationIntent. Currently there is no way to select or include these parameters in the connection string.
Alternatively, adding a field to the credential to be able to manually specify additional parameters (ie MultiSubnetFailover=TRUE;), or allowing for a manually written entire connection string would also provide this support, such as this request.
My use case:
Currently, n8n cannot properly connect to a SQL Server Database that participates in an availability group spanning multiple subnets.
Without the MultiSubnetFailover parameter the connection must be made directly to the ‘primary’ server in the availability group. This avoids any redundancy in the SQL Server enviroment and n8n’s connection must be manually updated in the event of a ‘failover’ to a different server.
Specifying ApplicationIntent would allow read-only connections to be executed on secondary servers to improve load-balancing.
I think it would be beneficial to add this because:
This would simplify and improve integrating n8n with SQL Server databases in the above described environment and allowing it to take full advantage of databases in SQL Server Availability Groups.