Execute Stored Procedure

**NOTE: This plug-in is deprecated and no longer recommended for use for sites running on Appian 22.1 or later. The functionality of this component is available in Appian without installing the plug-in. You can use a!executeStoredProcedureForQuery(), a!executeStoredProcedureOnSave(), or the Execute Stored Procedure Smart Service in Appian 22.1 or later.**

Overview

This plug-in provides a Smart Service and Function for executing stored procedures. The Smart Service can be used to execute stored procedures that modify data. Result sets are returned as CDTs. As custom functions cannot have side-effects, it must not be used to execute stored procedures that modify data. It is only safe to use the Smart Service with stored procedures that modify data. Following SQL Statements should not be used by the stored procedures executed with the function:

  • INSERT
  • UPDATE
  • DELETE
  • TRUNCATE
  • CREATE TEMPORARY TABLE
  • SELECT... INTO (when the input target is not an input or output variable)

Key Features & Functionality

  • Works with both complex and simple data types
  • Tested with: MySQL, SQL Server, and Oracle
  • See the instructions document provided with the download for an example and how to configure
  • (New) Total row count column added to trace log
Anonymous
Parents
  • This plug in has a cloud badge. So - will work with the Appian Cloud database - MariaDB?

  • Hi Juergen! Yes this works with Appian Cloud and MariaDB

  • Hi Pete,
    Thanks for the confirmation. 

  • We are only using the smart service at this point so I can't comment on the function, but as noted above the function is not supposed to be used to modify data, only read. Most of our critical path processes use write to data store smart services, but a few do use procedures. We have observed no issues with procedures- that includes modifying the DB as well.

  • Hi - we have recently upgraded to 20.4 with Maria DB and also have extensive use of the Stored Procedure plug in.

    So far all of our Smart Service calls have been ok - which perform create, read, update and delete statements. 

    We also ensured that any use of the stored procedure function in expressions and script tasks were limited to read functions.

    We have had a niggle with one stored proc returning inconsistent results but on the whole the Plug In still operates as it did on MySQL. Bearing in mind that if you are on Cloud DB, the function warned users not to use this with procedures that created data due to GTID enforcement.

    Hope this helps. 

    As with all upgrades though thorough testing is highly recommended.  

    Cheers 

    Paul

  • Hello

    reading Migration to MariaDB guidelines, I've read that this plugin has some problems with procedures that modify database (insert, delete, update etc..). Is this true? In the application we developed for our main customers we use procedures for this purpose, is this a problem? Is it only related to functions or even to smart services?

    Thanks in advance

    Best Regards

    Stefano

Comment
  • Hello

    reading Migration to MariaDB guidelines, I've read that this plugin has some problems with procedures that modify database (insert, delete, update etc..). Is this true? In the application we developed for our main customers we use procedures for this purpose, is this a problem? Is it only related to functions or even to smart services?

    Thanks in advance

    Best Regards

    Stefano

Children
  • We are only using the smart service at this point so I can't comment on the function, but as noted above the function is not supposed to be used to modify data, only read. Most of our critical path processes use write to data store smart services, but a few do use procedures. We have observed no issues with procedures- that includes modifying the DB as well.

  • Hi - we have recently upgraded to 20.4 with Maria DB and also have extensive use of the Stored Procedure plug in.

    So far all of our Smart Service calls have been ok - which perform create, read, update and delete statements. 

    We also ensured that any use of the stored procedure function in expressions and script tasks were limited to read functions.

    We have had a niggle with one stored proc returning inconsistent results but on the whole the Plug In still operates as it did on MySQL. Bearing in mind that if you are on Cloud DB, the function warned users not to use this with procedures that created data due to GTID enforcement.

    Hope this helps. 

    As with all upgrades though thorough testing is highly recommended.  

    Cheers 

    Paul