Happy 8th birthday to the Maveryx Community! Take a walk down memory lane in our birthday blog, and don't miss out on the awesome birthday present that all Maveryx Community members get to take advantage of!

Alteryx Designer Desktop Knowledge Base

Definitive answers from Designer Desktop experts.

Stored Procedures FAQ

Alteryx Alumni (Retired)

Stored Procedure FAQ

What are Stored Procedures?

Stored Procedures are a set of SQL statements (i.e., a subroutine) that are saved as a group and given a name so that the process can be easily reused and shared.

Why use Stored Procedures?

A benefit of the Stored Procedures is that you can centralize data access logic into a single pane that is then easy for the database administrators (DBA) to optimize. Stored procedures also have a security benefit in that you can grant execute rights to a Stored Procedures but an individual user will not need to have read/write permissions on the underlying tables.

Which Databases are Stored Procedures Supported for in Alteryx?

  1. Microsoft SQL Server
  2. Oracle
  3. SAP Hana

Which Tools can Stored Procedures be Accessed From?

Stored Procedures are only accessible using the standard Input tooland the Dynamic Input tool. More information can be found here Choose Table or Specify Query Window.

When using a Stored Procedure with the Dynamic Input Tool, the Value should be unique so that it is easily replaced in the Update Stored Procedure mode.

How are the Stored Procedures Executed when they are Called from Alteryx?

The Alteryx engine is not used when executing a stored procedure. The execution happens entirely on the database server.

How Do I Create Stored Procedures, and Execute them in Alteryx?

Below are a series of examples that walk you through from creating the Stored Procedures (SP) through the execution of them inside of Alteryx.

Example 1: SQL Server

In SQL Server Management Studio:

Use [Digan]  Create PROCEDURE Order_Priority AS Select * FROM [Demo].[dbo].[US_Transactions_Demo]

Here, I am creating a Stored Procedure (SP) in my [Digan] database that is selecting all the records from my US_Transactions_Demo table. This SP will bring back all the columns and records within the US Transitions Demo table.

Alteryx View:

After you connect to the database, click on the Stored Procedure tab and you should see a list of all the SP’s you should have access too. Below we see our Order_Priority SP that we just created.


SQL Editor Tab:

In the SQL Editor Tab, it should automatically populate based on the SP you have just select. In our case, it is:

EXEC Order_Priority

Running the Workflow:

The results should look like below. As described earlier, it should bring back the full table.


Example 2: Adding User Parameters

In this example, we are going to add user parameters to the SP. This should return the results based on the user's input.

In SQL Server Management Studio:

The Order_Priority_CriticalFilter SP below is adding a user input, @Order_ Priority, and grabbing all the records where the Order_ Priority column is equal to the user input.

Create PROCEDURE Order_Priority_CriticalFilter @Order_Priority nvarchar(30) AS Select * FROM [Demo].[dbo].[US_Transactions_Demo] WHERE [Order_Priority]=@Order_Priority

Alteryx View:

Here my user input for Order_Priority column filter is set to ‘Critical’. Make sure you respect the datatype of the SP. If it is a string, make sure to add the quotes around the parameter.


SQL Editor Tab:

EXEC Order_Priority_CriticalFilter 'Critical'

This is automatically populated from the Stored Procedure Tab.

Running the Workflow:


In the results, we see only the results where the Order_Priority is equal to Critical.

Example 3: Multiple User Inputs with Aggregations

Creating the SP in a SQL Server:

Create PROCEDURE Order_Priority_Most_Sold_Items @Product_SubCategory nvarchar(max), @Order_Priority nvarchar(max) AS Select [Product_Sub-Category], 
count([Product_Sub-Category]) as 'Category Count',
sum([Sales]) as 'Sum Sales'
FROM [Demo].[dbo].[US_Transactions_Demo] WHERE [Product_Sub-Category]=@Product_SubCategory AND [Order_Priority]=@Order_Priority GROUP BY [Product_Sub-Category], [Order_Priority]

In this example, we are creating an SP that is going to have 2 user inputs, Product_SubCategory and Order_ Priority.

In the SP, we are doing the following:

  1. Grabbing the Product_Sub-Category, Order_Priority, and the Sales column.
  2. Using the count function to get the occurrence of the Product_Sub-Category table and renaming the column to 'Category Count',
  3. Finding the total sales (sum clause) and renaming that column to 'Sum Sales'.
  4. Filtering based on the user input by Product_Sub-Category and Order_Priority.
  5. Lastly, Grouping by Product_Sub-Category and Order_Priority to get the aggregation of the table.

Alteryx View:

Here my user input for Product_Sub-Category is set to ‘Labels’ and Order_Priority is set to ‘Not Specified’.


SQL Editor Tab:

EXEC Order_Priority_Most_Sold_Items'Labels', 'Not Specified'

Running the Workflow:


Grabbing all Stored Procedures in the given database

The best way to grab all the SP’s in a given database is to use the information_schema. As long you are not in the master database, system stored procedures will not be returned.

select *    from DB_NAME_HERE.information_schema.routines   where routine_type = 'PROCEDURE'

If for some reason, you have a non-system SP in the master database, you can query:

select *    from master.information_schema.routines   where routine_type = 'PROCEDURE'     and Left(Routine_Name, 3) NOT IN ('sp_', 'xp_', 'ms_')

Note, this will filter out MOST system Stored Procedures. More information for Stored Procedures can be found here.

5 - Atom

Hi @DiganP,


I'm using the Input Data tool to try to run my SP. My SP is currently sitting in SQL and can be executed without a problem via SQL itself and even using the run command line on my computer. The issue comes when I try to use Alteryx. In your example above, it seems that my SP should pop up after I connect to my database (pop up on the Stored Procedures tab). That tab is blank for me and I'm unable to add anything.



5 - Atom

I am also unable to see stored procedures

6 - Meteoroid

I tried a slightly different version of the procidure shown in the example. In the procidure used below, the result is temporary, but Alteryx is unable to read the return giving the following error message:




Does anyone know if we actually have this limitation when we use alteryx to consume a procidure that returns a select from a temporary table?


Proc exemple:









I have tried with a more complex proc and have the same problem:



7 - Meteor



Thanks for the information. Can we use the system variable such as 'workflow name ' as a value in stored procedure execution? Help appreciated!!!




8 - Asteroid

Dear Alteryx Team/Community, 


are there any plans to add Snowflake to the list of databases that can call stored procs via Alteryx? Given the partnership between the two companies it would be a quite nice to have feature. 


What's the best work around to call a stored proc via Alteryx if stored procedures are not supported via the pre-SQL statement in the input tool? We are thinking of integrating a python module and try that way but we'd prefer a simpler solution. 




5 - Atom

I agree with Thomas who mentioned above that adding the capability to execute Snowflake stored procedures within the INDB tools would be a great feature.  We could potentially use Alteryx to orchestrate jobs within our Snowflake environment this functionality, for example.


Could this be as simple as being able to adjust the INDB tool to not create a CTE on the back end SQL call, so it doesn't add a "select *" in front of the procedure call within the SQL editor?


i.e., if I enter "CALL PROC_XYZ" into my INDB tool when connected to Snowflake and execute, I see Snowflake trying to run ( Select * from "CALL PROC_XYZ" ), causing a syntax error resulting in a failed query.


Does anyone have a work around for this, or are there plans to add this capability soon?




For ORACLE, stored procedures are only supported through the pre/post SQL statements.  Stored procedures are not displayed in the Stored Procedures Tab in VQB.