Configuring available server connections for a workspace
When you add a database connection to a project, or export data to an external database, you select the server connection to use.
From the Server Connections section of the workspace settings page, you manage the available server connections for the workspace.
When you create a server connection during data export, during database connection creation, you can choose whether to add the connection to the workspace server connections list.
Adding a server connection
From the Server Connections list, to add a server connection:
Click Add Server Connection.
On the New Server Connection panel, to use a connection string to populate the connection fields, in the Connection URL field, paste the string. When it uses a connection string to populate the fields, Fabricate sets Name to the host value. You can change the name to a different value.
If you do not use a connection string, then:
Under Platform, click the server platform.
In the Name field, provide a name to use to identify the server connection.
Provide the connection details.
To test the connection, click Test Connection.
Note that for Google BigQuery, Fabricate prompts you to provide a dataset to use for the connection test.
To save the connection, click Create Server Connection.
Editing a server connection
To edit a server connection:
Click the edit icon for the server connection.
On the connection details panel, update the connection details. Note that Fabricate does not display the existing content of password, secret, or private key fields. If you are not changing those values for a server connection, then leave the field empty.
To test the updated configuration, click Test Connection.
To save the changes, click Save Changes.
Connection details
Platforms other than Databricks, Google BigQuery, or Snowflake
For platforms other than Databricks, Google BigQuery, or Snowflake, the connection fields are:
In the Host field, provide the hostname for the server.
In the Port field, provide the port to connect through.
From the SSL/TLS dropdown list, select whether to enable or require Secure Socket Layer (SSL) or Transport Layer Security (TLS).
Some platforms include
verify-caandverify-fulloptions. For those options, you must add the required certificate to the account certificates list.
Selecting the authentication method
For the following connection types, from the Authentication dropdown list, select the type of authentication to use:
PostgreSQL
MySQL
SQL Server
Amazon Redshift
Other platforms always use a username and password.
The options are:
Username & Password. This is the default.
AWS IAM Role. To use this option, you must first configure the available AWS roles for the workspace. Note that this option is not available for SQL Server.
Azure AD Service Principal. To use this option, you must first configure the available Azure service principals for the workspace. Note that this option is not available for Amazon Redshift.
Providing a username and password
For username and password authentication:
In the Username field, provide the username to use to make the connection.
In the Password field, provide the password.
Providing an AWS role
For AWS IAM role authentication:
In the Username field, provide the username to use to make the connection.
From the AWS Role dropdown, select the role to use.
Providing an Azure service principal
For Azure AD service principal authentication:
In the Username field, provide the username for the Microsoft Entra user to use to make the connection. The user must be mapped to the service principal that you select.
From the Azure Service Principal dropdown, select the service principal to use.
Databricks
For Databricks:
In the Host field, provide the host where the database is located.
From the Credential Type dropdown list, select the type of authentication to use. The options are:
Service Principal
Personal Access Token
For Service Principal authentication:
In the Client ID field, provide the client identifier.
In the Secret field, provide the secret that is associated with the client identifier.
For Personal Access Token authentication, in the Access Token field, provide the access token to authenticate to the database.
In the Warehouse ID field, provide the data warehouse for the data.
Google BigQuery
For Google BigQuery:
In the Google Cloud Project ID field, provide the identifier of the Google Cloud project where the data is located.
In the Service Account Key field, provide the service account key to use to connect to the project. How to generate a service account key.
In the Location field, specify the location of the project. If you do not provide a location for the server connection, then when you connect to a dataset, Fabricate uses the dataset to determine the location.
Note that when you test a Google BigQuery server connection, Fabricate prompts you to provide a dataset to use for the connection test.
Snowflake
For Snowflake:
In the Account Identifier field, provide the identifier for the Snowflake account that owns the connection.
From the Credential Type dropdown list, select the type of credentials to use for the connection. The options are:
Password
RSA Key Pair
If you select Password:
In the Username field, provide the username for the connection.
In the Password field, provide the password for the connection.
If you select RSA Key Pair:
In the Username field, provide the username for the connection.
In the Private Key field, paste an unencrypted, PEM-encoded private key.
In the Warehouse field, provide the name of the warehouse that runs the connection.
In the Role field, provide the name of the role to use for the connection.
Deleting a server connection
You cannot delete a server connection that is either:
Used in a database connection.
The server connection for a database export target. Before you can delete the server connection, you must remove the export target.
From the Server Connections list, to delete a connection, click its delete option.
Last updated
Was this helpful?