Action group: Databases
The action executes a call to a stored procedure with parameters. Compatible with MS SQL Server
Property | Description | Type | Filling example | Mandatory field |
Parameters | ||||
DB context | Connection context to the selected database | Robin.DbContext | Database context | Yes |
Stored procedure name | Stored procedure name | Robin.String | Yes | |
Parameters list | A collection of parameter values to be substituted into a stored procedure call | Robin.Collection | No | |
Results | ||||
Results of a stored procedure execution | Collection of stored procedure results. Each result is a data table If result is a row set then data table contains it. If result is an update count then data table contains one column "update_count" and one row with the value. Hint: if you don’t need update counts just use in stored procedure operator suppressing return of counts. For MS SQL Server - SET NOCOUNT ON | Robin.Collection |
A stored procedure is prepared SQL code that will be saved so that the code can be reused over and over again.
So if you have a SQL query that you write over and over again, save it as a stored procedure and then just call it to execute it.
You can also pass parameters to the stored procedure so that the stored procedure can act based on the parameter values passed in.
Creating a stored procedure
Executing a stored procedure
More about stored procedures here.
Connect to the database and get the entire Organizations table
using the previously created stored procedure
Use the actions "Connect Standard Db", "Call Stored Procedure", "Get value by index", "Table to CSV".
The program robot completed successfully. The collection that contains the resulting table was returned.