Replaces an existing procedure with a modified version. Include the entire modified procedure in the ALTER PROCEDURE statement, and reassign user permissions on the procedure.
Syntax 1
ALTER PROCEDURE [ owner.]procedure-name procedure-definition
Syntax 2
ALTER PROCEDURE [ owner.]procedure-name REPLICATE { ON | OFF }
Syntax 3
ALTER PROCEDURE [ owner.]procedure-name SET HIDDEN
Syntax 4
ALTER PROCEDURE [ owner.]procedure-name RECOMPILE
Syntax 5
ALTER PROCEDURE [ owner.]procedure-name ( [ parameter, …] ) [ RESULT (result-column, ...)] EXTERNAL NAME ‘external-call’ [ LANGUAGE environment-name ] }
The ALTER PROCEDURE statement must include the entire new procedure. You can use PROC as a synonym for PROCEDURE.
The ALTER PROCEDURE statement is identical in syntax to the CREATE PROCEDURE statement.
With ALTER PROCEDURE, existing permissions on the procedure are not changed. If you execute DROP PROCEDURE followed by CREATE PROCEDURE, execute permissions are reassigned.
If SET HIDDEN is used, debugging using the debugger does not show the procedure definition, and the definition is not available through procedure profiling.
You cannot combine Syntax 2 with Syntax 1.
The procedure definition is not changed by recompiling. You can recompile procedures with definitions hidden with the SET HIDDEN clause, but their definitions remain hidden.
iq-environment-name: JAVA [ DISALLOW | ALLOW SERVER SIDE REQUESTS ]:
DISALLOW is the default.
ALLOW indicates that server-side connections are allowed.
Do not use UDFs with both ALLOW SERVER SIDE REQUESTS and DISALLOW SERVER SIDE REQUESTS in the same query.
When using the ALTER PROCEDURE statement for table UDFs, the same set of restrictions apply as for the CREATE PROCEDURE Statement (External Procedures).
Must be the owner of the procedure or a DBA. Automatic commit.