Defining the SQL External Stored Procedure | Teradata Vantage - Defining the SQL External Stored Procedure - Analytics Database - Teradata Vantage

After you register the JAR file containing the class or classes that implement the external stored procedure, you can define the SQL external stored procedure with the CREATE PROCEDURE or REPLACE PROCEDURE statement.

Database for the External Stored Procedure

When you execute the CREATE PROCEDURE or REPLACE PROCEDURE statement to define an external stored procedure that is implemented by a class in the JAR file, you must define it in the same database in which the JAR file was registered.

Specifying the Class Name, Method Name, and JAR Identifier

The CREATE PROCEDURE and REPLACE PROCEDURE statements provide the EXTERNAL NAME clause for specifying the identifier of the registered JAR file, and the class and method name in the JAR file that implements the external stored procedure.

Consider the following CREATE PROCEDURE statement:

CREATE PROCEDURE GetReport(INOUT Str VARCHAR(120))
   LANGUAGE JAVA
   READS SQL DATA
   PARAMETER STYLE JAVA
   EXTERNAL NAME 'Report_JAR:report.getReport';

where:

Specifying the Type of Data Access

If the external stored procedure does not use JDBC to execute SQL, the CREATE PROCEDURE or REPLACE PROCEDURE statement can specify the NO SQL data access clause to indicate that the external stored procedure does not execute SQL.

For more information and an example, see Executing SQL in Java External Stored Procedures.

Default and Temporary Paths

To manage external stored procedures, Teradata uses default and temporary paths for external stored procedure creation and execution, including a temporary directory where external stored procedures are compiled.

For information, including the names of external stored procedure default and temporary paths, see Teradata Vantage™ - Database Administration, B035-1093.

Related Information