You can create a connection to a Microsoft Azure SQL database from the Trifacta platform. This section describes how to create connections to Microsoft SQL DB.
- This connection type supports data ingestion into ADLS/WASB. When large volumes of data are read from an Azure SQL database during job execution, the data is stored in a temporary location in ADLS/WASB. After the job has been executed, the data is removed from the datastore. This process is transparent to the user.
- For more information on Azure SQL DB, see https://azure.microsoft.com/en-us/services/sql-database/.
- If you haven't done so already, you must create and deploy an encryption key file for the Trifacta node to be shared by all relational connections. For more information, see Create Encryption Key File .
To create this connection:
- Search Microsoft SQL Server in Import Data Page.
For additional details on creating a SQL DB connection, see Enable Relational Connections.
This connection can also be created using the above property substitutions via CLI or API. You must create a connection of SQL Server type.
- For details on values to use when creating via CLI or API, see Connection Types.
- See CLI for Connections.
- See API Connections Create v3.
This connection is a SQL Server connection type with special settings for some properties. Please create a SQL Server connection and then modify the following properties with the listed values:
Enter your hostname. Example:
|Port||Set this value to |
|Connect String options|
Please insert the following as a single string (no line breaks):
Tip: If you have access to the SQL DB database through the Azure Portal, please copy the Connect String from that configuration. You may omit the username and password from that version of the string.
|User Name||Username to use to connect to the database.|
|Password||Password associated with the above username.|
|Default Column Data Type Inference|
For more information, see Database Browser.
For more information on how values are converted during input and output with this database, see SQL Server Data Type Conversions.
This page has no comments.