Microsoft SQL Server

Microsoft SQL Server destination plugin example

Latest: v4.2.0

In this article we will show you a simple example of configuring Microsoft SQL Server destination plugin.


In order to be able to sync to Microsoft SQL Server you will need a running installation. We will be using the quickstart guide (opens in a new tab) for running Microsoft SQL Server locally using Docker.

Create admin password for Microsoft SQL Server

Microsoft SQL Server enforces password complexity. In order to successfully run the database you must specify a password that adheres the policy described here (opens in a new tab).

For this example we will be using yourStrongP@ssword as a password.

Start Microsoft SQL Server locally

docker run \
  -e "ACCEPT_EULA=Y" \
  -e "MSSQL_SA_PASSWORD=yourStrongP@ssword" \
  -p 1433:1433 \
  -d \

Create database to sync to

We will be using cloudquery for database name in this example.

docker exec $(docker ps -alq) \
  /opt/mssql-tools/bin/sqlcmd \
  -U "SA" \
  -P "yourStrongP@ssword" \
  -Q "CREATE DATABASE cloudquery;"

Note: docker ps -alq returns container ID for the latest started container. You can use container ID discovered manually via docker ps output instead.

Configure Microsoft SQL Server destination plugin

Once you've completed the steps from Prerequisites section you should be able to connect to the local cloudquery Microsoft SQL Server database via the following connection string:

server=localhost;user id=SA;password=yourStrongP@ssword;port=1433;database=cloudquery;

The (top level) spec section is described in the Destination Spec Reference. The full configuration for Microsoft SQL Server destination plugin will look like this:

kind: destination
  name:     "mssql"
  registry: "github"
  path:     "cloudquery/mssql"
  version:  "v4.2.0"

    connection_string: "server=localhost;user id=SA;password=yourStrongP@ssword;port=1433;database=cloudquery;"

Make sure you use environment variable expansion in production instead of committing the credentials to the configuration file directly.