You can use Adobe Workfront Fusion to connect to Microsoft SQL Server.
You must have the following access to use the functionality in this article:
|Adobe Workfront plan*||
Pro or higher
|Adobe Workfront license*||
|Adobe Workfront Fusion license**||
Current license requirement: No Workfront Fusion license requirement.
Legacy license requirement: Workfront Fusion for Work Automation and Integration
Current product requirement: If you have the Select or Prime Adobe Workfront Plan, your organization must purchase Adobe Workfront Fusion as well as Adobe Workfront to use functionality described in this article. Workfront Fusion is included in the Ultimate Workfront plan.
Legacy product requirement: Your organization must purchase Adobe Workfront Fusion as well as Adobe Workfront to use functionality described in this article.
To find out what plan, license type, or access you have, contact your Workfront administrator.
For information on Adobe Workfront Fusion licenses, see Adobe Workfront Fusion licenses.
You can execute your custom logic directly on your database server through stored procedures. Adobe Workfront Fusion loads interface of input/output parameters and recordset dynamically so each parameter or value can be mapped individually. Before you start configuring your scenario, make sure the account you’re using to connect to your database has read access to
When Fusion establishes the connection to the SQL server destination, the Fusion user identifies the Host (the domain name or IP address where the server is hosted) and the port. Fusion can connect to any available host and port.
For information about specific IP addresses used by Workfront Fusion, see IP Addresses for accessing Adobe Workfront Fusion
To learn more about creating a stored procedure, see the Microsoft SQL Server documentation.
Workfront Fusion doesn’t support multiple recordsets. Only the first one is processed.
This error occurs when you modify the same data using multiple modules. It is caused by SQL transactions.
When any SQL module is executed, it starts a transaction. The transaction is finished after the scenario is fully executed.
If another module tries to access the same data, it has to wait until the previous transaction is finished. Since the first transaction will be finished after the scenario is finished, the second transaction can never begin.
Turn on Auto-commit. Auto-commit finishes (commits) every transaction immediately after the module execution is done.