Authenticating a connection to Microsoft SQL Server enables communication between the two platforms. This must be successfully added before Form Connectors can push or Data Sources can pull data.
In this article
- Adding
- Authenticating
- Connection String
- Additional Info
- Troubleshooting Tips
- TLS Version Error
Adding
The Connections area of the platform is where you can add connections for connectors. Navigate the side menu to Connected Data > Connections.
On the Connections page:
- Click the ADD CONNECTION button on the top right to bring up a list of connections.
- Click on the SQL Server option.
Authenticating
After adding a connection, fill in the required properties and save.
Connection String
Add the SQL Server Connection String to be used by connectors to access your database.
Windows Authentication is NOT supported; you must include username and password credentials in the string.
Encrypt Connection Checks if your SQL Server has a valid certificate installed to ensure the Connector uses SSL encryption for all data sent between the Platform and your SQL Server.
Click the SAVE button on the top right to store your configuration and automatically verify the connection.
Additional Info
- SQL connections are only available on Premium accounts, and users must be Administrator level to see the option.
- The SQL user-specified MUST have at least db_ddladmin and db_datawriter database-level roles assigned.
For the most straightforward configuration, grant db_owner role to the user.
- You must configure your database firewall to accept connections from our cloud servers.
Get a list of our platform's cloud IP addresses by raising a ticket to technical.support@dowo.digital
Troubleshooting Tips
To help you get your SQL connection working as quickly as possible, we've listed some common connection errors that you might encounter and how you can resolve them.
TLS Version Error
If your SQL connection fails with the error message:
A connection was successfully established with the server, but then an error occurred during the login process. (provide: SSL Provider; error: 0 - An existing connection was forcibly closed by the remote host)
The error message suggests that your SQL server does not support TLS 1.2.
All communications between our platform and external servers require support for the TLS1.2 security protocol as a minimum.
To remedy this issue, an upgrade/update on your SQL server might be necessary to enable TLS 1.2 or higher. If this is the case, then you will need to contact your IT team to request this upgrade.
Once your server has been updated, you should see that the Connection will start working.
Check if your database server is configured for TLS1.2 or higher communication.
