Calling a procedure in MySQL ETL flow

user073741

I'm trying to create a pivot table output using a stored procedure, but I'm getting an error while call the procedure.

 

 

when I to execute the procudure, I'm getting the error as:

Let me know what wrong I'm doing here. 

 

Thanks in Advance,

Srinivas V

jaeW_at_Onyx

@user073741 ,

 

i would start by paring back my stored proc to ensure that i had the proper syntax for CREATE-ing and calling a stored proc.  keep in mind we're on mysql v 5.6 i believe.

 

THEN i would take a really close look at the error message.

 

it says <number> FROM.

 

I would guess that you have values in your table that contain spaces so SQL is 'mininterpreting' how to handle table creation, OR you're not properly separating the values as column names in your GROUP_CONCAT statement in a way that SQL can interpret into separate columns.

 

Try taking your SQL statement out of the Stored PROC and running it as a straight SELECT statement.  Make sure the results are as you expect.

 

LASTLY, MySQL is not strong at Pivot Statements.  Consider using MagicETL.  I know it's a pain to setup and ideally you don't want to have to maintain code, but long term it will probably be more performant than SQL.

jaeW_at_Onyx

@user073741 ,

 

i would start by paring back my stored proc to ensure that i had the proper syntax for CREATE-ing and calling a stored proc.  keep in mind we're on mysql v 5.6 i believe.

 

THEN i would take a really close look at the error message.

 

it says <number> FROM.

 

I would guess that you have values in your table that contain spaces so SQL is 'mininterpreting' how to handle table creation, OR you're not properly separating the values as column names in your GROUP_CONCAT statement in a way that SQL can interpret into separate columns.

 

Try taking your SQL statement out of the Stored PROC and running it as a straight SELECT statement.  Make sure the results are as you expect.

 

LASTLY, MySQL is not strong at Pivot Statements.  Consider using MagicETL.  I know it's a pain to setup and ideally you don't want to have to maintain code, but long term it will probably be more performant than SQL.

user073741

Thanks.

 

As you correctly mentioned, The column names were not getting populated correctly from the procedure. Executed the code manually and found that out.