Introduction

This article describes how to add more than one parameter value to a stored procedure value.

Current Behaviour in the Call Stored Procedure (OLEDB) Tool

Dynamic values for stored procedures come from recordset columns, variables, formulas, or functions. You drag the required value from the Task Browser to the Value column in the Call Stored Procedure (OLEDB) The Call Stored Procedure (OLEDB) tool executes database stored procedures and functions to provide read, write, and automated data processing.'s Main tab:

If you try to drag over an additional value placeholder, it replaces the original placeholder with the new one.

Adding More Than One Value

To add additional values, you must manually enter these.

Placeholders for dynamic values, such as recordset columns, variables, formulas, and functions, are written using VBScript syntax. Each distinct value must be encapsulated in curly brackets { }, followed by an equals sign =. Use the following syntax, replacing the values in <italics> with your own task values:

Recordset Columns

Syntax

If using a RecordSource column property from the Call Stored Procedure (OLEDB) step (where Scope = This Step):

{=ThisStep.RecordSource("<column_name>")}

Example

{=ThisStep.RecordSource("ACCOUNT_REFERENCE")}

This uses the value from the ACCOUNT_REFERENCE column in the recordset consumed by the Call Stored Procedure (OLEDB) step.

Syntax

If using a RecordSource or RecordSet column property from any other task step (where Scope = Task):

{=Steps("<step_name>").<recordset_type>("<column_name>")}

Example

{=Steps("DBQ-GetOrders").RecordSet("ORDER_NUMBER")}

This uses the value from the ORDER_NUMBER column in the recordset outputted by the DBQ-GetOrders step.

Variables

Syntax

{=Variables("<variable_name>")}

Example

{=Variables("TriggerAccountRef")}

This uses the value from the variable named TriggerAccountRef.

Formulas

Syntax

{=Eval(Formula("<formula_name>")}

Example

{=Eval(Formula("FormGetDate")}

This uses the evaluated result from the FormGetDate formula.

Functions

Syntax

{=<function_name>()}

Any Other Task Browser Property

For a detailed description of all available task browser properties, refer to the product help, Task Browser Properties.

Syntax

If using a property from the Call Stored Procedure (OLEDB) step (where Scope = This Step):

{=ThisStep.<property>}

Example

{=ThisStep.StatusText}

This uses the value from the StatusText property of the Call Stored Procedure (OLEDB) step.

Syntax

If using a property from any other step (where Scope = Task):

{=Steps("<step_name>").<property>}

Example

{=Steps("DBQ-GetOrders").Started}

This uses the timestamp for when the DBQ-GetOrders task step was started.

Syntax

If using a task property:

{=Task.<property>}

Example

For example, {=Task.Version} provides the task version number.