You are not logged in.
I had a job using a tAggregateRow that failed because of memory space. I found out that I could use the tAggregateSortedRow instead and not only my memory
problem was solved but it even ran quicker. The trouble is the output is not the same and a row is missing in the new job.
I have put and ran the 2 jobs together to show the problem. There is 1 line difference in the output as shown in the image. The input file is the same, so are the other
component other than the tSortRow, whose set up is also in the picture.
The pictures were made from a simplified example of the real job. None the less the error is the same. Whether I use a delimited file or a tMSSqlInput as source,
I get the same problem and it consistently occurs on the last record (of the table or the file).
Has someone seen this before, has an idea for why it happens ?
I'm using TOS 4.2.2 on Win2008 64bits
Last edited by bcastell (2012-01-04 17:01:17)
that sounds like a component bug to me. You can issue a bug in the bugtracker and get updates on when it is fixed: