DSXchange

Hi bhs,

getting the same error message today when reading a nvarchar(max) column out of SQL Server using ODBC connector.

Your workaround may help me.

Thanks and regards,
Hendrik

Hi,
apart from a proper function name and syntax, is there (really) no need to validate input data in format "%dd%mm%yyyy" as well?
You could get data like 29022011 or 00102010 which would generate error logs ...

Ok,
what source are you talking about? DB, Flat file?
What is the datatype of your input column? CHAR, VARCHAR?

Hi,

just an idea: maybe could you identify an empty line by its length using length function len().

And what does empty line mean?
Number of Blanks? NULL?

Actually I have run this procedure successfully for no input parameters So I thought that there is no need to tell you the place where to keep the query ... Place it here: Stage tab > Syntax > Procedure call syntax Did you specify your output variable / column in Parameter tab? The error message yo...

Also please tell me that why you kept double quotes for some input arguments and single quotes for other? Does it depend upon the data type of my input argument? Yes it depends, for calling that sample stored procedure I had to use ... single quote for date double quotes for string no quote for int...

Hi, maybe this sample about calling a DB2 procedure via stored procedure stage helps: CALL #$DB2SCHEMA#.PROC_NAME(#PARAM1#, '"#PARAM2#"','"#PARAM3#"','#PARAM4#','#PARAM5#',?,?,?,?,?,?,?,?); Values for input variables provided by #Parmaters#, output variables represented by "...

Why using so much stages variables? :? You could group the data in the sort stage (by TableName) and then use the created key change column in one stage variable in transformer. The syntax of <stagevar>: If KeyChange Then 1 Else <stagevar> +1 That's what I meant with grouping / transformer logic in ...

Just to make it more clear for me ... Source Table contains data like this: TABLE_NAME --------------- A A B B B ... And you want to achieve this: TABLE_NAME COUNTER --------------- ----------- A 1 A 2 B 1 B 2 B 3 ... If this is your requirment I would think about some grouping / transformer (stage ...

I am not sure if I got your requirements right, just an idea ...

Put the the two jobs in a separate Sequence without any links to make them run in parallel.
Then run this Sequence in a loop out of another one ...

Ok, if your calculation should be done on a daily base, just add the billing date to your keys in the aggregator stage ...

Taking a further look at your sample data (on the first group only) ... Buss unit | Cust code| product key |Seq no |Billing Date | Amount| 5001 AAT 1230 1 jan06 0.12 5001 AAT 1230 1 jan06 0.87 If Billing Date is not part the key construction, this could also be, right? Buss unit | Cust code| product...

Maybe you could provide some sample data for the 6 input columns and the aggregated (and partly calculated) result data set ...?
Maybe it would make sense NOT to use the aggregator stage for your requirements.

Which DB stage do you use for custom sql?

In case of using the DB2 Connector for example try this ...

update table_name set column_a = column_a * orchestrate.percent where key_1=orchestrate.key_1 ;

'orchestrate' means taking the column value out of the ETL flow at runtime

Hi guys, I already put the main question in the subject field. For some testing purposes I created a simple parallel Job: Reading from Sequential File Stage (using a schema file and RCP)--> Copy Stage (using RCP) --> writing data to PEEK stage I let the job run and started the automated services in ...