This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I frequently load data to staging tables in SQL and then run a stored procedure via the Post SQL setting in the output tool to merge it in with the destination tables. I'm finding that if the stored procedure fails due to some error, Alteryx often doesn't notify me. Instead it simply acts like it completes fine.
To reproduce this, I created a simple stored procedure:
CREATE PROCEDURE STG.TEST
SELECT 1 AS TEST INTO #TEMP
SELECT 1/0 AS Calc INTO #TEMP2
When I run this via SSMS, I get this error as expected:
(1 row affected) Msg 8134, Level 16, State 1, Procedure STG.TEST, Line 12 [Batch Start Line 15] Divide by zero error encountered. The statement has been terminated.
When I run this via a post SQL statement in the Alteryx output tool, the workflow runs fine without displaying the error:
This is a serious issue because without these errors getting passed through, a user has no warning that the data was not successfully loaded.
Has anyone else encountered this? Interestingly if I set NO COUNT ON then the error does get passed through. This implies that if any records are successfully written to a table (in this case a temp table) then Alteryx will ignore any subsequent errors that are generated.