[SQL Server] Execute
Q100019: [SQL Server] Execute
Executes a SQL command on specified SQL Server.
| Parameter | In/Out | Description | Other Info |
|---|---|---|---|
| DB connection | In | Assign a defined SQL Server Connection or directly enter the parameters and values which make up a valid connection for SQL Server. |
Connection type: sysSqlServer |
| SQL command | In | SQL statement or command(s) to be executed. | |
| Command timeout seconds | In | Timeout in seconds for the command to execute. Default is 0 seconds, the same as SSMS, which will wait indefinitely. | Default: 0 |
| Run within transaction | In | When true will execute the SQL command within a transaction. | Default: true |
| Log output level | In | Choices: Minimal, VerboseThe level of execution detail you want to appear in the log. |
Default: Minimal |
| Execution output | Out | Text returned by PRINT statements in SQL being executed. | |
| Result code | Out | Result code returned from the command containing any UPDATE, INSERT, or DELETE statements is the number of row affected by the query. Any other type of command returns a value of -1. |
(Italics = required parameters)
Notes
The [SQL Server] Execute module is built for executing commands on a specified SQL Server. The module requires that a SQL Server Connection is defined for communicating with the desired SQL Server. Supplying the SQL Command parameter with the SQL statement you want executed on the SQL Database will submit the command to the database server. All commands are normally executed in an implied transaction. Since certain special commands cannot be executed in a transaction, such as the built in Backup command, the option for Run within transaction would need to be set to false to disable the implied transaction.
Last Updated:
10/3/2023 1:06:51 AM