Information
  • Author: Appian Corporation
  • Type: Plug-in (Function & Smart Service)
  • Support: This plug-in or utility is not supported by the author. The content is free to use with a licensed product, but it is made available as-is and Community supported.
  • Industry: All Industries
  • Compatible Version(s): 18.4+
  • First Released:
  • Last Updated:
  • Cost: Free
Resources
Share
Home » AppMarket » Execute Stored Procedure

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

  • Hi, just stumbled over a bug when using nvarchar(max) in SQL Server 2016.

    I am fetching a base64 encoded document with output defined as nvarchar(max). When using the execute SP plugin the data gets cutoff after 4000 characters. I tried it with the deprecated data type ntext. With ntext I get back the complete data.

    Also tested this directly with the SP. There ntext and nvarchar(max) return the full data. Therefore I think it's an issue within the Execute SP Plugin.

    Please have a look. Thanks.

Comment

  • Hi, just stumbled over a bug when using nvarchar(max) in SQL Server 2016.

    I am fetching a base64 encoded document with output defined as nvarchar(max). When using the execute SP plugin the data gets cutoff after 4000 characters. I tried it with the deprecated data type ntext. With ntext I get back the complete data.

    Also tested this directly with the SP. There ntext and nvarchar(max) return the full data. Therefore I think it's an issue within the Execute SP Plugin.

    Please have a look. Thanks.

Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.