Last updated
Last updated
This section describes the syntax for subprogram invocations within PL blocks, such as procedures or anonymous blocks.
For more information on this subject, please refer to Oracle's Subprogram documentation: ()
Procedure calls can be migrated to Snowflake as long as there are no optional parameters and their order matches the formal parameters. Please note that Procedure invocations get migrated to a Call statement.
Snowflake Scripting has support for this statement, albeit with some functional differences.
Snowflake does not support setting default values for parameters. So these will need to be filled into every call.
These parameters will not cause any compilation errors when ran in Snowflake; however, calls still place them in a positional manner. For this reason, the order of these parameters needs to be checked. SnowConvert does not support checking nor reordering these parameters.
This sample contains manual intervention for some functional differences and is used to explain them. For more information on these differences, please check the below.
Snowflake does not have support for parameter modes, however, a solution is being implemented to emulate their functionality. To get more information about the transformation for output parameters please go to the following article .
: Default Parameters May Need To Be Reordered.
: Element with missing dependencies.
Translation reference for PROCEDURE CALL aka SUBPROGRAM INVOCATION