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.
3 weeks ago
When running a Stored Procedure from the Input or Dynamic Input tool the following error (or similar) will occur.
Error opening "EXEC StoredProcedure": "No Columns Returned"
Both Input tool as well as the Dynamic Input tool require in the main SQL section a statement that returns columns.
Amend the Stored Procedure to return columns by modifying the SQL query of the Stored Procedure on the database side. If you are unsure how to do that you can work on it together with your DBA.
Connect using an OLEDB connection instead of an ODBC connection and re-test the Stored Procedure as is.Alternatively, the Stored Procedure can be called within the Pre- or Post-SQL query section of the Input tool.
If you have further questions feel free to reach out to Customer Support by sending an email to email@example.com.
The resolution above also works when no Stored Procedure is used. If the SQL statement in the Query slot doesn't return any data, for example, because it just modifies a table, the No Columns Returned error will occur because the Input Data and Dynamic Input tools require that some data be returned even if you don't need that data and don't use it anywhere in your workflow.
SELECT 1 AS dummy from DUAL;
works for Oracle.Other databases don't even require a table be specified
SELECT 1 AS dummy;
works for SQL Server.