DSXchange

Sometimes the database columns have default values set. Maybe thats in play here.

Thanks Paul.

A quck search turned out this. Give it whirl.
viewtopic.php?t=135583&highlight=Curren ... mpMS%28%29

But I would suggest saving the logs in a flat file or table which will help during debugging. You dont want to be without your joblog when trying to debug your job.

Did not know there was a function for timestamp with milliseconds. Good to know.

Millisecs huh. Ping the database and grab it as a string.

Thanks Ernie. During sunset the hue in the sky is amazing, filled with colors, combine that with calm waters and there you go.

Either do a count(*) so that you have an incoming row or use row generator. Bottom line is, you need an input row for there to be an output row. I have done this in the past by doing count(*). If the result is 0, I would put the current timestamp else I would branch the execution to run my appropria...

And when you have records you are just getting max timestamp or timestamp for each row?

O. Sorry about that. Missed that.
But if there are no records there is no timestamp right? So you have to decided what timestamp value you need to put if there are no records.

Just thought id share my gallery with you folks. Whenever you guys need to give your upper left brain a rest, check out my snaps at

http://n0mi.500px.com

Sure, drag another link from the database stage doing a count. I like to keep it separate, hence my advice.

Have a seperate job do a count(*). This way you will always have a single row output regardless.

The name says it all.

Boolean is just a TRUE or FALSE. If you extract as varchar you will see a 0 or 1. Try doing that.