Microsoft SQL Server

Integromat Updated October 21, 2020 18:58

Getting started with Microsoft SQL Server (MSSQL)

The above modules let you execute your custom logic directly on your database server through stored procedures. Integromat loads interface of input/output parameters and recordset dynamically so each parameter/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 INFORMATION_SCHEMA.ROUTINES and INFORMATION_SCHEMA.PARAMETERS views.

Integromat will make connections to your database from the following IP range: 82.208.14.110 - 82.208.14.119.

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

Notes

Integromat doesn't support multiple recordsets, only the first one is processed.

Troubleshooting

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 then it starts the transaction (1) and the transaction is finished after the scenario is fully executed.
If another module tries to access the same data used in another unfinished transaction (1) then it has to wait until the previous transaction (1) is finished – but it never happens because the first transaction (1) will be finished after the scenario is finished.

Solution

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

1. Open Scenario settings.

2. Enable the Auto commit checkbox.

3. Confirm the settings dialog by clicking the OK button.