...
Excerpt | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Supported Relational DatabasesThe
Additional relational connections can be enabled and configured for the platform. For more information, see Connection Types. PortsFor any relational source to which you are connecting, the
Please contact your database administrator for the host and port information. EnableThis feature is enabled automatically. To disable:
Disable relational publishingBy default, relational connections are read/write, which means that users can create connections that enable writing back to source databases.
As needed, you can disable this feature. Steps:
Publishing through relational connections is disabled. |
Limitations
Info |
---|
NOTE: Unless otherwise noted, authentication to a relational connection requires basic authentication (username/password) credentials. |
- You cannot swap relational sources if they are from databases provided by different vendors. See Flow View Page.
There are some differences in behavior between reading tables and views. See Using Databases.
...
Info |
---|
NOTE: Writing back to the database utilizes the same user credentials and therefore permissions as reading from it. Please verify that the users who are creating read/write relational connections have appropriate access. |
...
- You cannot ad-hoc publish to a relational target. Relational publishing is only supported through the Run Job page.
- You write to multiple relational outputs from the same job only if they are from the same vendor.
- For example, if you have two SQL Server connections A and B, you can write one set of results to A and another set of results to B for the same job.
- If A and B are from different database vendors, you cannot write to them from the same job.
...