Microsoft SQL Server SSH (data source)

Microsoft SQL Server is a relational database management system created by Microsoft. SSH integration differs from traditional integration in that it connects to the database through an intermediate server, also called a tunnel or bastion.

SQL Server SSH data integration for Data Warehouse created by Kondado enables you to have access to SQL Server SSH data in your analytics cloud.

Adding the data source

To automate SQL Server SSH ETL with Kondado for your database, follow the steps below:

1) Allow the Kondado IPs on the database server (and in your VPC) for the port that will be used to connect with the SQL Server

2) On the database server, allow the connection to the intermediary server on the port that will be used

3) On the Kondado platform, go to add data sources and select the Microsoft SQL Server SSH data source

4) Give your data source a name and fill in the information for your intermediate server and then your database. In “Server PEM key” just copy the text of the file with the PEM key.

Now just save the connector and start replicating your SQL Server SSH data into the Data Lake or Data Warehouse.

Pipelines

Tables and Views

With our pipelines, you will be able to replicate tables as well as views
If your table has a datetime/timestamp type column that marks when a record was changed/inserted, your pipeline can be incremental
It will be necessary to define the primary key, which can be defined by several columns and refers to the column (or set of columns) that define a record as being unique

The table created in the destination will have a format similar to the one below:

Field	Type
col_x	text
col_y	text
col_z	text

Add Microsoft SQL Server SSH as a Data Source on Kondado

Configure a secure SSH tunnel connection to your Microsoft SQL Server database through an intermediary bastion server on the Kondado platform.

Allow Kondado IPs on your database server

Configure your database server and VPC firewall to allow incoming connections from Kondado IPs on the port used for SQL Server. This is the first security layer for your secure data integration.

Enable connection to the intermediary server

On the database server, allow outbound connections to your SSH bastion/tunnel server on the port that will be used for the tunnel.

Select the Microsoft SQL Server SSH connector

Log in to the Kondado platform, navigate to add data sources, and choose the Microsoft SQL Server SSH data source from the available connectors.

Configure the SSH tunnel and database credentials

Give your data source a name, then fill in the intermediate server (bastion) details followed by your actual database connection info. For "Server PEM key", paste the full text content of your PEM key file.

Save and start replicating data

Save the connector configuration. You can now begin replicating your SQL Server SSH data into your Data Lake or Data Warehouse, with support for both tables and views.

Set up incremental replication if applicable

For incremental pipelines, ensure your table has a datetime/timestamp column tracking record changes/insertions, and define the primary key (which may span multiple columns) to uniquely identify records.

Frequently asked questions

What is the difference between SQL Server SSH integration and traditional SQL Server integration?▼

Traditional integration connects directly to the database, while SSH integration routes the connection through an intermediary server (tunnel or bastion). This adds a security layer by not exposing your database directly to external connections. You can learn more about secure connections on our security page.

What do I need to prepare on my infrastructure before adding the SQL Server SSH source?▼

You need to allow Kondado IPs on your database server and VPC for the SQL Server port, and also allow the database server to connect to your intermediary/bastion server on the SSH port. Both firewall rules are required for the tunnel to function.

Where do I find the PEM key for the Server PEM key field?▼

The PEM key is a cryptographic key file provided by your system administrator or generated when setting up your SSH bastion server. Open the .pem file in a text editor, copy the entire text content (including BEGIN and END markers), and paste it directly into the "Server PEM key" field in the Kondado connector setup.

Can I replicate both tables and views from SQL Server SSH?▼

Yes, Kondado pipelines support replication of both tables and views from your SQL Server SSH source into your destination Data Lake or Data Warehouse.

What is required to set up incremental replication for SQL Server SSH?▼

For incremental replication, your table needs a datetime or timestamp type column that records when each row was inserted or last modified. You must also define a primary key, which can consist of one or multiple columns that together uniquely identify each record.

Where can I send my SQL Server SSH data after replication?▼

After configuring your source, you can replicate data into a Data Lake or Data Warehouse. From there, explore available destinations such as BI tools, spreadsheets, or other analytics platforms to consume your data.

Written by

Thassyo Pereira·Published 2023-07-18·Updated 2026-04-25