Microsoft SQL Server

Microsoft SQL Server (MS SQL Server or even SQL Server) is a Microsoft relational database that is behind many applications, being one of the most popular databases in the world. By using SQL Server as a data destination on the Kondado platform, you can create your Data Warehouse quickly.

 

Click here to access the tutorial on how to connect to your visualization tool:
Looker Studio
Power BI

 

Click here if you don't have a Microsoft SQL Server database to use as a data warehouse and want to create one on Azure

To automate the ETL for your SQL Server data warehouse with Kondado, follow the steps below:

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

2) On the Kondado platform, go to the add new destinations page and select the SQL Server data destination

3) Name your destination and fill in your database information:

Address: Use the IP or DNS of your database for external access

Port: Fill in the port to be used for access (usually 1433)

Database: fill in the database of your database (if you don't know the value of this parameter, you can create a new one following these instructions)

User: database access user. This user must have DROP, INSERT, CREATE, ALTER, SELECT and DELETE permissions

Password: User access password to the database

Now you can save the destination and start using SQL Server as your Data Warehouse!

Add SQL Server as a Data Destination on Kondado

Configure Microsoft SQL Server as your data warehouse destination on the Kondado platform by allowing IP access and entering your database credentials.

1
Allow Kondado IP addresses on your database server

Configure your SQL Server database server (and VPC) to allow Kondado's IP addresses on port 1433, the standard port for SQL Server connections. This ensures secure external access for the ETL pipeline.

2
Select SQL Server on the Kondado destinations page

On the Kondado destinations page, click to add a new destination and choose the SQL Server data destination from the available options.

3
Name your destination and enter connection details

Provide a clear name for your destination, then fill in the Address (IP or DNS for external access), Port (typically 1433), Database name, and credentials for your SQL Server instance.

4
Configure database user permissions

Ensure your database user has the required permissions: DROP, INSERT, CREATE, ALTER, SELECT, and DELETE. These permissions allow Kondado to fully manage your data integration and warehouse operations.

5
Save and start using SQL Server as your Data Warehouse

After verifying all fields are correct, save the destination. You can now use SQL Server as your Data Warehouse and connect it to visualization tools like Looker Studio or Power BI for analysis.

Frequently asked questions

What is Microsoft SQL Server and why use it as a data destination?
Microsoft SQL Server is one of the world's most popular relational databases, powering many applications. Using it as a data destination on Kondado lets you quickly create a Data Warehouse for centralized analytics.
What port does SQL Server typically use for connections?
SQL Server typically uses port 1433 for connections. You must allow Kondado's IP addresses on this port in your database server and VPC firewall rules.
What database permissions does the Kondado user need?
The database user must have DROP, INSERT, CREATE, ALTER, SELECT, and DELETE permissions. These allow Kondado to manage tables and data during the ETL process.
Can I create a new SQL Server database if I don't have one?
Yes. The article mentions you can create a new database if you don't know the existing database value, and also provides a link to create a Microsoft SQL Server database on Azure if you don't have one at all.
Which visualization tools can I connect to after setting up SQL Server?
After configuring SQL Server as your destination, you can connect visualization tools like Looker Studio and Power BI. Kondado also supports data-to-dashboards workflows with various BI platforms.
Do I need to allow Kondado IPs in my VPC as well as the database server?
Yes, you should allow Kondado's IP addresses both on the database server itself and in your VPC (Virtual Private Cloud) to ensure proper network access for the ETL pipeline.

Written by·Published 2023-07-06·Updated 2026-04-25