Rebinding a Procedure
A procedure depends on one or more underlying sources, and the procedure is considered “bound” to those underlying sources.
The following procedure bindings are available:
|
•
|
A SQL script can be bound to a table or a procedure. |
|
•
|
A transformation can be bound to hierarchical data (XML or WSDL). |
|
•
|
A packaged query can be bound to a data source. |
Rebinding a procedure is useful:
|
•
|
If after creating a procedure you decide to rebind the procedure to different sources. |
|
•
|
If an execution error occurs because a source no longer exists and you want to rebind the procedure with a new source. |
If you modify a procedure or its dependencies, the binding is automatically updated when you save the script, and the Rebind panel reflects the change. For example, if your procedure has a data source dependency named ds_orders, and you rename it ds_orders_renamed and save the script, the Rebind panel lists the dependency as ds_orders_renamed.
To rebind a procedure to a different source
|
2.
|
Click the Show Rebind Panel toolbar button. |
The Rebind panel opens in the lower section of the procedure editor, and displays the immediate dependencies as determined by the last-saved version of the procedure. (If a procedure has never been saved, the Rebind panel is blank.)
|
3.
|
In the Rebind panel, highlight the source in the left pane and click Rebind. |
|
4.
|
In the Rebind dialog that opens, specify the source with which to rebind the script and click OK. |