I have a situation in which the query to be executed itself would be passed as a context parameter from the parent job.
The query string is approximately 1250 characters. When i try to print the query - am able to print them all (no truncation of character), but when i pass that as parameter and execute in a tmssql component, it is showing a column as Invalid.
Example : Query String (not real query though)- SELECT A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P from dbo.Table (of length 1250).
Issue - The error message is tMSSqlInput_1 Invalid column name 'K'. If i remove column 'K' the error says Invalid Column 'L'. But when i pass 'SELECT * FROM dbo.table' or 'SELECT A,B,C,D,E,F,G,H,I,J from dbo.Table' it is running fine. I checked tens of times all the columns i mentioned here are available in Table.
Someone, please help me to unveil this issue.
Does it work when you run it directly on the MSSQL? double checking MS SQL engine, skip Talend ...
Looks weird indeed!
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Watch the recorded webinar!
Part 2 of a series on Context Variables
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema