Page History
...
If your stored procedure does not return a result set, then you should use the SQL_CALL activity instead. Refer also to the description of the SQL_CALLQRYCSV activity for an alternate way to receive the result set from a stored procedure call.
This activity supports the use of SQL parameter markers (usually designated by a question mark) in the SQL statement. If your solution uses this capability, you must first execute one of the following activities to supply the parameter value(s):
Set parameter values for SQL operation | |
Set parameter values for SQL operation from CSV |
...
For more information about the SQL database activities, refer to the description of the SQL_CONNECT activity. For a list of supplied working (*) examples using the SQL database activities, refer to:
Example Processing Sequences using the SQL database activities
INPUT Parameters:
SQLHANDLE: Required
This parameter must specify the connection handle value that identifies the SQL connection upon which this activity should operate. The connection handle value is returned by the SQL_CONNECT activity.
SQLCALL: Required
...
The SQL statement may make use of parameter markers (usually designated by a question mark). You must use either the SQL_PARAMS or the SQL_PARAMSCSV activity before this activity, to supply the parameter values. Note that the SQL_CALLQUERY activity will make use of only one set (or "row") of parameter values.
The following is an example that might be specified in this parameter to call the SQL stored procedure DXTUTSQL01, passing it two parameter values that have previously been supplied using either the SQL_PARAMS or the SQL_PARAMSCSV activity:
DXTUTSQL01(?, ?)
...