Troubleshooting Relational Connections
This section provides generic information on how to troubleshoot your relational connections.
Problem - Unable to access customer encryption key
When trying to create, edit, or test a relational connection, you may receive the following error message:
400 - Encryption Key Error. Please Contact Administrator: Unable to access customer encryption key.
You are unable to access the relational source.
The encryption keyfile is missing from the Alteryx deployment, or the keyfile has been moved without updating the platform of the new location.
You must create and deploy this keyfile, which is required for ensuring that encrypted usernames and passwords are used in relational connections.
Note
This keyfile must be created and deployed before any relational connections are created. Deployment requires access to the file system on the Trifacta node.
After you have deployed the keyfile, you must configure the platform to point to its location. A platform restart is not required.
For more information, see Relational Access.
Problem - Retrieving sample data for large relational tables is very slow
In some cases, you may experience slow performance in reading from database tables, or previews of large imported datasets are timing out.
In these cases, you can experiment with the number of records that are imported per database read. By default, this value is 25000.
To improve performance, you can modify the following setting.
You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
"data-service.sqlOptions.limitedReadStreamRecords": 25000,
To improve performance, you can try lowering this limit incrementally. Avoid raising this limit over 100000, which can overwhelm the browser.