---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Create a Microsoft SQL Server connection

# Create a Microsoft SQL Server connection {#ariaid-title1}

Release version: Australia  
Updated September 30, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Create a zero-copy connection to Microsoft SQL Server to access relational database data in Zero Copy Connector Hub without moving or duplicating data.

## Before you begin

Role required: df_connection_admin

## About this task

Table statistics are enabled by default for Microsoft SQL Server connections.

After you create this connection, data stewards can use it to create data fabric tables that map to Microsoft SQL Server data sources. For additional information about connecting, see [Microsoft SQL Server connector documentation](https://trino.io/docs/current/connector/sqlserver.html).

## Procedure

1. Navigate to the available primary connectors in Zero Copy Connector Hub in one of the following ways:
   * Navigate to AllZero Copy Connector HubAvailable connectorsPrimary connectors.
   * Navigate to AdminZero Copy Connector HubAvailable connectorsPrimary connectors.
   {#create-sqlserver-connection-zcc__choices_n5p_vrt_k2c}
2. Locate the Microsoft SQL Server connector and select Connect.
3. Complete the connection form.  
   {#create-sqlserver-connection-zcc__table_sqlserver_conn_form__entry__2}

   | Field | Description |
   |-|-|
   | Name and description ||
   | Connection label | Unique name for this connection. This helps in identifying the connection within your system. |
   | Connection name | System-generated name based on the Connection label. This field cannot be modified once the connection is established. |
   | Short description | Description of the connection explaining what it is about. |
   | Connection attributes ||
   | Connection URL | JDBC URL to establish the connection. For example: * Azure SQL:<kbd class="ph userinput">jdbc:sqlserver://&lt;server&gt;.database.windows.net:1433;database=&lt;db&gt;;encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;loginTimeout=30</kbd> * GCP or on-premises:<kbd class="ph userinput">jdbc:sqlserver://&lt;host&gt;:1433;databaseName=&lt;db&gt;;encrypt=true;trustServerCertificate=true</kbd> {#create-sqlserver-connection-zcc__ul_lt2_lkl_tkc} The `encrypt` and `trustServerCertificate` parameters in the URL are optional. Setting SSL in the Connection security configurations section is the recommended approach; if you specify these parameters in the URL, they take precedence over that setting. |
   | SSL | Option to enable or disable SSL for the connection. When Enabled, additional fields appear based on the selected SSL mode, Server Certificate Source, and Store type. See [Microsoft SQL Server connection security configuration fields](https://www.servicenow.com/docs/QyiQb_jF9TzfXdwfuXHnPw "Fields that appear under Connection security configurations on the New Microsoft SQL Server Connection form depending on the selected SSL mode.") for the complete conditional field set. |
   [Table 1. Microsoft SQL Server connection form]

   {#create-sqlserver-connection-zcc__table_sqlserver_conn_form}
4. Configure the authentication method that you want to use with Microsoft SQL Server.

   | Option | Description |
   | Basic | Option to use a Microsoft SQL Server login username and password. Compatible with all Microsoft SQL Server deployments, including Azure SQL, GCP Cloud SQL, AWS RDS, and on-premises. 1. Enter the username associated with the source. 2. Enter the password associated with the username. {#create-sqlserver-connection-zcc__ol_sqlserver_basic} |
   | OAuth | Option to authenticate using OAuth. Note: Azure SQL Server supports OAuth for this connector. AWS RDS and GCP Cloud SQL don't support IAM or token-based authentication for Microsoft SQL Server at the platform level, so use Basic authentication for those deployments. This is a cloud-provider limitation, not a limitation of the connector. Select the OAuth credential type that you want to use. * Azure Service Principal: option to enter OAuth credentials directly from Azure AD (Entra ID). See [Microsoft SQL Server authentication method fields](https://www.servicenow.com/docs/oElBoGk2etPD~lKe581BTw "Fields that appear on the New Microsoft SQL Server Connection form depending on the selected OAuth credential type.") for the specific fields (Azure tenant ID, Azure client ID, Azure client secret, Azure token scope). * Access Token: option to use an existing OAuth entity profile, with either a shared (System) or per-user (Personal) integration type. See [Microsoft SQL Server authentication method fields](https://www.servicenow.com/docs/oElBoGk2etPD~lKe581BTw "Fields that appear on the New Microsoft SQL Server Connection form depending on the selected OAuth credential type.") for the specific fields (OAuth entity profile, Select OAuth integration type). {#create-sqlserver-connection-zcc__ul_sqlserver_oauth_credential_type} |
   |-|-|

   {#create-sqlserver-connection-zcc__choicetable_sqlserver_auth}
5. Select Connect.
{#create-sqlserver-connection-zcc__steps_xvd_wck_tkc}

## Result

A test connection is made to the external data source, verifying that the connection details are correct and the data source is accessible.

## What to do next

If the connection succeeds, configure data steward access on the Access Control tab. See [Manage access to an established connection using roles](https://www.servicenow.com/docs/lH57CuH3kSJT8KypBiimsA "Manage which data stewards can access an established connection and create data fabric tables.").

If the connection fails, verify the connection details with your data source administrator and try again.
**Related reference**   

* [Microsoft SQL Server connection security configuration fields](https://www.servicenow.com/docs/QyiQb_jF9TzfXdwfuXHnPw "Fields that appear under Connection security configurations on the New Microsoft SQL Server Connection form depending on the selected SSL mode.")
* [Microsoft SQL Server authentication method fields](https://www.servicenow.com/docs/oElBoGk2etPD~lKe581BTw "Fields that appear on the New Microsoft SQL Server Connection form depending on the selected OAuth credential type.")

*[\>]: and then