Connecting to SQL Server or SQL Azure

Skyvia supports usual unencrypted connections and secure SSL connections to SQL Server or SQL Azure. Note that for connecting both to SQL Server and to SQL Azure, you need to select the SQL Server connector when creating a connection.

To connect to a SQL Server server, you need to specify the database server host name or IP address, the user name and password to login, and the database name.

Skyvia supports SQL Server 2019, 2017, 2016, 2014, 2012, 2008, and 2005.

note Important Note

Skyvia requires your SQL Server to be accessible from the Internet. Skyvia will access your server from the IP

You can find some advices on configuring your SQL Server in order to access it from Skyvia in the How to Configure Local Database Server to Access It from Skyvia topic.


You need to specify the following parameters for TCP/IP SQL Server connection:

Name - connection name that will be used to identify the connection on the Connections page and when selecting a connection for a package.
Server - the name or IP address of the SQL Server instance to which to connect. Here you also specify the SQL Server named instance name and, if necessary, port, in one of the following formats:
tcp:<IP>\<named instance>
Here IP is the IP address or domain name of the SQL Server computer, named instance is the name of the corresponding SQL Server named instance, and port is the SQL Server port.
The port part is necessary only if your SQL Server uses a non-default port number. Otherwise, comma and port may be omitted.
User Id - the user name to login with.
Password - the password to login with.
Database - the name of the SQL Server database you want to connect to.


If you want to use SSL connection, additionally you need to click the Advanced button and set the following parameters:

Encrypt - determines whether to use SSL encryption for all data sent between the client and server if the server has a certificate installed.
Trust Server Certificate - determines whether the channel will be encrypted while bypassing walking the certificate chain to validate trust.

On the Advanced tab you can also set the Command Timeout interval. It specifies the wait time before terminating an attempt to execute a command and generating an error. Note that it is the time to wait for any server reply since the command was sent to a server, and it doesn't include the time necessary to fetch data if the command selects some data.

Additionally the Advanced parameters include the Connection Timeout parameter. This parameter determines the time (in seconds) to wait while trying to establish a connection before terminating the attempt and reporting an error. Generally you don't need to modify it, but in some specific cases when a connection to the database server is not good you may try increasing its value.


Connecting to SQL Azure

When connecting to SQL Azure, you need to select the SQL Server connector and specify the Server value in the following format:


The port part (with the comma) is usually not necessary; it is required only when the port, configured on the server, differs from the default one.

You can use the IP address instead of the server DNS name, but this is not recommended, because an IP address of an Azure virtual machine may change when Azure moves resources for redundancy or maintenance. You can get the server DNS name in the following way:

1.In the Azure Management Portal select VIRTUAL MACHINES.
2.On the VIRTUAL MACHINE INSTANCES page, under the Quick Glance column, find and copy the DNS name for the virtual machine.

The port can be found in the following way:

1.In the Azure Management Portal find the Virtual Machine.
2.On the Dashboard, click ENDPOINTS and use the PUBLIC PORT assigned to MSSQL.