--- title: Microsoft SQL Server slug: mssql image: https://make-cxp-documentation.ams3.cdn.digitaloceanspaces.com/apps-center-icons/PREVIEW_DEFAULT.png docTags: createdAt: 2025-02-03T13:28:13.883Z --- | | With the Microsoft SQL Server app in Make, you can run your custom logic directly on your database server through stored procedures. Make loads the interface of input and output parameters and record sets dynamically so each parameter/value can be mapped individually. | | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | # Requirements To use the Microsoft SQL Server app in Make, you must make sure sure the account you're using to connect has read access to `information_schema.routines` and `information_schema.parameters` views. If SSL encryption is enabled, a valid SSL certification must be obtained. **Supported Versions:** SQL Server 2012/2014/2016/2017/2019/2022 # Connect Microsoft SQL Server and Make To create the connection: ::::WorkflowBlock :::WorkflowBlockItem Log in to your Make account, add a Microsoft SQL Server module to your scenario, and click **Create a connection**. ::: :::WorkflowBlockItem Optional: In the ​​**Connection name​​** field, enter a name for the connection. ::: :::WorkflowBlockItem Enter information for the following fields: | **Field** | **Description** | | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Host** | Enter the Microsoft SQL Server host. | | **Port** | Enter the port. This must be a number between 1 and 65535. | | **User** | Enter your user name. | | **Password** | Enter your password. | | **Database** | Enter the Microsoft SQL Server database. | | **Transaction Isolation Level** | Select your transaction isolation level.
For more information, read the [Microsoft transaction locking and row versioning guide](https://learn.microsoft.com/en-us/sql/relational-databases/sql-server-transaction-locking-and-row-versioning-guide?view=sql-server-ver15). | | **Encrypt** | Select **Yes** or **No**. | | **Trust Server Certificate** | Select **Yes** or **No**. | ::: :::WorkflowBlockItem Click **Save**. ::: :::WorkflowBlockItem If prompted, authenticate your account and confirm access. ::: :::: You've successfully created the connection and can now use the Microsoft SQL Server app in your scenarios. If you want to make changes to your connection in the future, follow the steps [here](docId\:SO88FM6pkT0G-adKDDfzZ). # Microsoft SQL Server modules After connecting to the Microsoft SQL Server app, you can use the following types of modules to build your scenarios. ## Actions - Delete row(s) from a table - Execute a query (advanced) - Execute stored procedures - Insert row into a table - Update row(s) in a table ## Searches - Select row(s) from a table ## Feeders - Iterate recordset # Troubleshooting the Microsoft SQL Server app The **ER\_Lock\_Wait\_Timeout: Lock wait timeout exceeded; try restarting transaction** 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 the transaction 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, then it has to wait until the previous transaction is finished – but it never happens because the first transaction will be finished after the scenario is finished. To solve this, turn on **Auto-commit**. It finishes (commits) every transaction immediately after the module execution is done. ::::WorkflowBlock :::WorkflowBlockItem Open the scenario sesttings. ::: :::WorkflowBlockItem Enable the **Auto commit** checkbox. ::: :::WorkflowBlockItem Click **OK** to confirm the settings. ::Image[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/wJmTbp9yPwqgXGa1d9DKr_uuid-6c7fca8f-92b8-55e8-5be0-bd64dc6107e6.gif" size="50" width="438" height="944" position="flex-start" showCaption="false"} ::: :::: # Microsoft SQL Server resources - [Microsoft SSL Configuration Guide](https://learn.microsoft.com/en-us/azure/mysql/single-server/how-to-configure-ssl) - [Microsoft SQL Server documentation](https://msdn.microsoft.com/en-us/library/ms345415.aspx)