Microsoft SQL Server
If SSL encryption is enabled, a valid SSL certification must be obtained.
Supported Versions: SQL Server 2012/2014/2016/2017/2019/2022
To create the connection:
Optional: In the Connection name field, enter a name for the connection.
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. |
Encrypt | Select Yes or No. |
Trust Server Certificate | Select Yes or No. |
Click Save.
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 . If you want to make changes to your connection in the future, follow the steps here.
- Delete row(s) from a table
- Execute a query (advanced)
- Execute stored procedures
- Insert row into a table
- Update row(s) in a table
- Select row(s) from a table
- Iterate recordset
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 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 is finished.
To solve this, turn on Auto-commit. It finishes (commits) every transaction immediately after the module execution is done.
