Back

Security information regarding on-premise Microsoft SQL Server-based connectors in Popdock

Published: Sep 15, 2025
Post Author Written by James Suhon

Microsoft SQL Sever-based Connectors in Popdock

When setting up a connector inside of Popdock to a Microsoft SQL Server (referred going forward as SQL)-based system, there are two common methods used. Both options are direct connections, act as a Popdock gateway, and have their own security that goes with them. This article will serve to explain the differences in security for both methods and what each entails, with corresponding articles linked into it.

Direct Connection

When setting up a direct connection in Popdock, the security is more open to customization than with a gateway. A direct connection allows you to keep the security as tight as you would like it to be. The main aspect of this type of connection is that it acts as a tunnel between Popdock and your SQL server that your data can flow through.

The two main pieces of this connection are firewall configuration and SQL user creation with assistance from TLS 1.2 encryption protocols. It is typically recommended to create a custom SQL user to be used in this connection, as it allows you to only give that user access to what is needed, rather than an SA user, who can access everything.

Other recommended setups are to utilize port forwarding on the firewall so that port 1433 (standard SQL port) is not directly exposed to the internet, as well as only whitelisting the Popdock IP address tied to your Popdock account region. This method’s setup depends on how tightly you want the security to be for this connection.

Gateway

The other method for connecting is with one of our Popdock gateways. These are installed onto a server of your choosing and run as a web service through the IIS on that server to act as a middleman for the connection that the data will travel through.

The security for this type of connection is more rigid in execution, as it will use an TLS (SSL) certificate and HTTPS security protocols for the primary security. A custom SQL user is also recommended for this method, with the same ideology as is explained in the direct connection section.

With this method, you can install the gateway on any server you have as long as it can connect with your SQL server internally. There are also additional methods of connecting with the gateway, as you can choose either a token authentication or a basic authentication, with the latter involving creating a username and password for the connection. These are both covered in the documentation for this process as well.

The gateway, as mentioned, can be set up anywhere. App servers, DMZ servers, or any other server will work as long as that server can communicate with whatever server your SQL is hosted on.

Popdock Connectors

Now you should have a better idea of the two options you have when setting up SQL-based connectors in Popdock. Depending on your security needs, you can choose between a direct connection or a gateway.

Have any questions on setting up SQL-based connectors in Popdock? Email support at support@eonesolutions.com 

Feeling stuck? Get the support and guidance you need to help you power through any data challenge

We're on your integration team. Connect with our people and let us know how we can help you.