This section describes how you interact with your databases through .
Read Access: Your database administrator must configure read permissions to the appropriate databases, tables and views for your use.
NOTE: To ensure that all user credentials used to access the database system are securely stored, you must first deploy the encryption key file to the . See Enable Relational Connections.
Database access is managed through connections.
NOTE: does not modify source data nor store transformed data in the relational systems. Datasets sourced from database tables or views are read without modification from their source locations.
You can create a from a table or view stored in a connected database.
Tip: In some scenarios, you can improve performance of loading from database tables by creating a view on the table to restrict the amount of data loaded to only the required fields. Additional, you can pre-filter the dataset using custom SQL statements. See Create Dataset with SQL.
For more information, see Database Browser.
NOTE: When executing a job using a relational source, the job may fail if one or more columns has been dropped from the underlying source table. As a workaround, the recipe panel may show steps referencing the missing columns, which be used to fix to either fix the recipe or the source data.
Relational connections can be configured to support writing results back to the database.
NOTE: You can only write to databases from the Run Job page. You cannot ad-hoc publish to a relational database.
NOTE: When writing to a new table in a relational target, the first entry in any mapping is used for writing out the value. Subsequent entries in the mapping are used for validation only on writing to new tables. See Connection Types.
Natively supported connection types are automatically enabled for writeback.