DSXchange

See if this post helps.

If you want the timestamp in YYYY-MM-DD hh:nn:ss format then run the following

I guess my explanation was'nt clear enough. Ray's explanation should put you to rest and answer your doubts.

Looking at your data, it seems like that the last row is missing the final tab before the null value.
For nullable fields, give a null_value in the extended properties and constraint on that value.

Hashed file stage is present in server jobs for lookups.

Do a select and load it to a flat file, just a few records. See if the date comes up as integers (internal format). If yes then no conversion is required, pass it as it is.

The post that I embeded has comments from our very best, Ray and Vincent. Adhere to their warning on when to use it, else there will be bottlenecks

What does the text file look like?
'SUCCESS' will be present in what column?
I presume the first column. Do Field() on the delimiter to get the first field and do comparison on that in your trigger expression.

Welcome Aboard
You can use OS level commands to get rid of such characters. Search for sed one liners or tr one liners on google.

Thank you guys for the encouraging note.
And narasimha, not Brian2B, BrianIAM
Thats what Others seem to think anyways.

In the extended properties, specify it as a Nullable field which you must have already done, I am sure. Specify the null_value to 0.

Has this routine ever worked before? Also set it as a Transform Routine and then test it out. See if it works Ok. Once it doesn, you can set it back to before/after routine. Are you sure you compiled your routine?

Yea, the Julian Day error is odd. As Craig mentioned, do a LEFT(in.Col, 10) and then do StringToTimestamp() on that. Load it to a flat file and see what happens?

Are'nt you getting the right output? What are you getting?

Not in the executable path, but there is a seperate place to specify parameters. Its the second box in execute command stage.