Stored Producer Runner

The Stored Procedure Runner Component is used to execute precompiled SQL logic stored in a database. A stored procedure is a named collection of SQL statements that are precompiled and stored in the database engine. This component enables pipelines to trigger those stored procedures on demand, passing input parameters and retrieving output parameters as needed.

Key Capabilities

• Run stored procedures across multiple supported databases.

• Pass input parameters dynamically from a pipeline.

• Capture output parameters returned by the stored procedure.

• Support for four major database drivers: MySQL, MSSQL, Oracle, PostgreSQL.

Configuration Overview

All Stored Procedure Runner configurations are grouped into the following sections:

• Basic Information

• Meta Information

• Resource Configuration

Configuring Meta Information

Database Connection

• Host IP Address – Enter the host IP address of the database server.

• Port – Enter the port associated with the host.

• Username – Provide the database username.

• Password – Provide the corresponding database password.

• Database Name – Enter the name of the target database.

Stored Procedure Details

• Procedure Name – Specify the stored procedure to execute.

• Driver – Select the driver for database connectivity. Supported drivers:

  • MySQL

  • MSSQL

  • Oracle

  • PostgreSQL

Parameters

• Input Parameters – Values passed into the stored procedure.

  • Each input parameter requires:

    • Name

    • Value

    • Type (e.g., String, Integer, Date)

• Output Parameters – Values returned by the stored procedure.

  • Each output parameter requires:

    • Name

    • Type

Example Use Cases

• Run a stored procedure that calculates monthly sales totals and returns them to the pipeline.

• Execute a stored procedure that archives processed records and confirms success via output parameters.

• Trigger a procedure for data validation before moving data into a warehouse.