Microsoft SQL Server

Overview

You can create a Microsoft SQL Server Destination Connector to write to a Microsoft SQL table by using your username and password.

The schema for this Destination Connector is defined by the Microsoft SQL table schema.

Prerequisites

Required information:

• Host

• Port

• Username

• Password

• Database

• SQL Server URL (Optional)

• Table

Creating an Microsoft SQL Destination Connector

Step 1: After selecting + New Connector, under the System prompt, click Microsoft SQL Server.

Step 2: Provide a Connector Name.

Step 3: Select Destination Connector.

Step 4: Provide the Host Name.

Step 5: Provide the Port Number.

Step 6: Provide your Username.

Step 7: Provide your Password.

Step 8: Provide the name of the Database that contains the table where data should be written.

If you are trying to access a database that is behind a firewall, please ensure that the following Osmos IP addresses are allowed to access the database. Osmos uses these fixed IP addresses to access your sources and destinations.

• 35.222.106.198/32

• 35.232.180.174/32

Step 9: Note, this field is optional and in most cases is best avoided. If your server instance is specifically configured, you may provide the SQL Server URL used to connect to your instance of Microsoft SQL Server, contact support for further details.

Step 10: Three display options are provided for tables within your database:

• Tables: If this option is selected, only tables will be displayed to connect to.

• Views: If this option is selected, only views will be displayed to connect to.

• Both: If this option is selected, both tables and views will be listed as valid connection options.

Step 11: Select the way you want like to enter data into SQL Server.

• Insert simply adds rows to the system

• Upsert first checks if the row exists - If it does it updates it, otherwise it inserts the row

Step 12: Provide the name of the Table where data should be written.

Note: the schema for this Destination Connector is defined by the Microsoft SQL Server table schema.

Note: for any fields that have primary key, foreign key or other constraints, you may either (1) ensure that the source data mapped to the field satisfies those constraints or (2) leave the field empty and ensure that your database is set up to auto populate those fields with appropriate constraint-satisfying data.

Advanced Options

Validation Webhook

We support the use of Validation Webhooks to prevent bad data from being written to your systems, adding another layer of protection to the built-in validations that Osmos provides. The Webhook URL can be posted here.

For more information on Validation Webhook configuration, see Server Side Validation Webhooks