Create SQL Server Connections

Contents:

You can create connections to one or more Microsoft SQL Server databases from Trifacta® Wrangler Pro.

If you are connecting Trifacta Wrangler Pro to any relational source of data, such as Redshift or Oracle, you must add the Trifacta Service to your whitelist for those resources.

For more information, see Getting Started with Trifacta Wrangler Pro.

Configure

To create this connection:

In the Import Data page, click the Plus sign. Then, select the Relational tab. Click the SQL Server card.
You can also create connections through the Connections page. See Connections Page.

Modify the following properties as needed:

Property	Description
Host	Enter your hostname. Example: testsql.database.windows.net
Port	Set this value to `1433`.
Connect String options	Insert any additional connection parameters, if needed. See below.
User Name	(basic credential type only) Username to use to connect to the database.
Password	(basic credential type only) Password associated with the above username.
Default Column Data Type Inference	Set to `disabled` to prevent the platform from applying its own type inference to each column on import. The default value is `enabled`.
Test Connection	After you have defined the connection credentials type, credentials, and connection string, you can validate those credentials.
Connection Name	Display name of the connection
Connection Description	Description of the connection, which appears in the application.

Reference

Connection URL

The properties that you provide are inserted into the following URL, which connects Trifacta Wrangler Pro to the connection:

jdbc:sqlserver://<host>:<port>;<prop1>=<val1>;<prop2>=<val2>

Connect string options

The connect string options are optional. If you are passing additional properties and values to complete the connection, the connect string options must be structured in the following manner:

;<prop1>=<val1>;<prop2>=<val2>...

where:

<prop> : the name of the property
<val> : the value for the property

delimiters:

; : any set of connect string options must begin and end with a semi-colon.
= : property names and values must be separated with an equal sign (=).

Example connect string options

The following connect string contains several options. Please insert as a single string (no line breaks):

;database=<database_name>;encrypt=true;trustServerCertificate=false;
hostNameInCertificate=*.database.windows.net;loginTimeout=30;

Common connect string properties:

Property	Description
`database`	Set this value to `<database_name>`, the name of the database to which to connect.
`encrypt`	Set this value to `true`. Encrypted communication is required.
`trustServerCertificate`	When set to `true`, the Trifacta node does not validate the SQL Server TLS/SSL certificate. Default value is `false`.
`hostNameInCertificate`	Defines the host name in the server certificate. NOTE: Do not modify this value unless required.
`loginTimeout`	Number of seconds that the Trifacta node attempts to login to the database server. Default is `30`.

Delimiters:

; : any set of connect string options must begin and end with a semi-colon.
; : all additional property names must be prefixed with a semi-colon.
= : property names and values must be separated with an equal sign (=).

Authentication options

Driver Information

This connection uses the following driver:

Driver name: com.microsoft.sqlserver.jdbc.SQLServerDriver
Driver version: com.microsoft.sqlserver:mssql-jdbc:7.2.2.jre8
Driver documentation:

Troubleshooting

Error message	Description
“The TCP/IP connection to the host <hostname>, port <port> has failed”	The host is not accessible. Please verify that the correct IP addresses have been whitelisted on the SQL Server instance. For more information, see Getting Started with Trifacta Wrangler Pro.
"Login failed for user '<username>'."	Permission denied. Please verify your credentials. Tip: Click the Test Connection button to check the connection credentials.
"The certificate received from the remote server was issued by an untrusted certificate authority"	There was an issue with the trusted certificate on the SQL Server instance. To disable validation of the certificate, add the following to the connection string options: ;trustServerCertificate=true;

Use

For more information, see Database Browser.

Data Conversion

For more information on how values are converted during input and output with this database, see SQL Server Data Type Conversions.

Send Feedback

Page tree