| Table of Contents |
|---|
...
Summary
...
Authentication on Manager
The Write-Back Manager requires an administrator account to access it. To log in, use the credentials defined through the email that the administrator received to register the administrator account.
Advanced Configuration
Configure Site
...
This configuration allows you to choose what is going to be the database repository that Write-Back is going to use to store its datasets. You can choose across a wide set of database technologies that include: PostgreSQL, SQL Server, Oracle, MySQL, SAP Hana, Vertica, Redshift, Snowflake, Exasol, and Google Big Query and this means you can store Wite-Back data side by side with your existing data.
| Info | ||
|---|---|---|
| ||
Write-Back has a fixed IP that will establish communication with your database, to ensure that you have to allow external to access to the database from IP address 13.82.49.25. It is highly recommended to create a specific database user for Write-Back to use. It should only have full access to the Write-Back schema where the datasets will be created. |
| Info | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
It is mandatory recommended to use a cloud database or ensure a compatible version.
|
...
| Expand | ||
|---|---|---|
| ||
In some cases, when using Snowflake, an error may indicate that there is an unsafe memory allocation or an out-of-bounds index. To fix this, please add |
| Expand | ||
|---|---|---|
| ||
In the case of BigQuery due to a lack of support for some operations on the database, there are the following limitations: |
Authentication
Here you can configure the authentication methods that include:
...