蜜豆视频

DocumentationWorkfrontWorkfront Guide

Microsoft SQL Server modules

Last update: Thu Nov 21 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • User

You can use 蜜豆视频 Workfront Fusion to connect to Microsoft SQL Server.

Access requirements

You must have the following access to use the functionality in this article:

蜜豆视频 Workfront plan*
Pro or higher
蜜豆视频 Workfront license*
Plan, Work
蜜豆视频 Workfront Fusion license**

Current license requirement: No Workfront Fusion license requirement.

Or

Legacy license requirement: Workfront Fusion for Work Automation and Integration

Product

Current product requirement: If you have the Select or Prime 蜜豆视频 Workfront plan, your organization must purchase 蜜豆视频 Workfront Fusion as well as 蜜豆视频 Workfront to use functionality described in this article. Workfront Fusion is included in the Ultimate Workfront plan.

Or

Legacy product requirement: Your organization must purchase 蜜豆视频 Workfront Fusion as well as 蜜豆视频 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 蜜豆视频 Workfront Fusion licenses, see 蜜豆视频 Workfront Fusion licenses.

Connecting the Microsoft SQL Server service to Workfront Fusion

For instructions about connecting your Microsoft SQL Server account to Workfront Fusion, see Create a connection to 蜜豆视频 Workfront Fusion - Basic instructions

NOTE
Some Microsoft apps use the same connection, which is tied to individual user permissions. Therefore, when creating a connection, the permissions consent screen displays any permissions that were previously granted to this user鈥檚 connection, in addition to any new permissions needed for the current application.
For example, if a user has 鈥淩ead table鈥 permissions granted via the Excel connector and then creates a connection in the Outlook connector to read emails, the permissions consent screen will show both the already granted 鈥淩ead table鈥 permission and the newly required 鈥淲rite email鈥 permission.

Using Microsoft SQL Server modules

You can execute your custom logic directly on your database server through stored procedures. 蜜豆视频 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鈥檙e using to connect to your database has read access to INFORMATION_SCHEMA.ROUTINES and INFORMATION_SCHEMA.PARAMETERS views.

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 蜜豆视频 Workfront Fusion

To learn more about creating a stored procedure, see the Microsoft SQL Server documentation.

NOTE
Workfront Fusion doesn鈥檛 support multiple recordsets. Only the first one is processed.

Troubleshooting error ER_LOCK_WAIT_TIMEOUT: Lock wait timeout exceeded; try restarting transaction

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.

Solution:

Turn on Auto-commit. Auto-commit finishes (commits) every transaction immediately after the module execution is done.

  1. Click the Scenario settings icon at the bottom of the screen.
  2. Click the Auto commit checkbox.
  3. Click OK to save the scenario settings.
recommendation-more-help
5f00cc6b-2202-40d6-bcd0-3ee0c2316b43