Microsoft SQL Server

true false 107false unhandled content type false unhandled content type requirements to use the microsoft sql server app in {{product name}} , 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 {{product name}} to create the connection log in to your {{product name}} account, add a microsoft sql server module to your {{scenario singular lowercase}} , and click create a connection optional in the ​​ connection name​​ field, enter a name for the connection enter information for the following fields true falsefalse left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type 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 {{scenario plural lowercase}} if you want to make changes to your connection in the future, follow the steps connect an application 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 {{scenario plural lowercase}} 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 singular lowercase}} 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 singular lowercase}} is finished to solve this, turn on auto commit it finishes (commits) every transaction immediately after the module execution is done open the {{scenario singular lowercase}} sesttings enable the auto commit checkbox click ok to confirm the settings microsoft sql server resources microsoft ssl configuration guide microsoft sql server documentation