DSXchange

You can certainly build a job that runs that source query with a parameter and then loop the job using a Sequence job. Each iteration could pass in a single value from a delimited list.

I thought that restriction was removed, what version are you running?

Anyway, have a transform wherever you use the stage variable and convert an empty string to null at that point.

Sequence jobs have nothing to do with configuring email on the ETL server. Just have your Admins ensure that you can send email from the command line on that server using normal UNIX functions like sendmail, mailx, etc. There's no Parallel routine as all of the notification happens before/after job ...

Help how? The question was to you. What do your requirements / rules say to do when all of the values in a particular column are null?

Moved to the correct forum.

This is your thread now, so if it is working to your satisfaction please mark the thread as Resolved using the button at the top of the page.

FYI - Un-hijacked the original post.

Any chance you could just check for one row in the file? Or could you get a one row file that is legitimate data (i.e. not just a timestamp) ?

I was going to say something about Server jobs if-then-else evaluations and not aborting over "null handling" when i realized while we may be in the Server forum, we seem to be talking about Parallel jobs here.

So off we go to the Enterprise forum...

Do both tables have the proper grants for the connecting user?

Your parens in this particular case don't add anything (as in change the behaviour) so no need for them. And one last time - all you need is the function call all by itself. I swear.

chrisjones wrote:My question is does the OR statement works in " if else statement"?

Yes, of course. Further help would require some detail around the "issue" that you are seeing.

There is chance to get Null data and '' data from source so that is the reason I am checking both. That's fine, doesn't change my answer. It's all unnecessary. All you are doing is checking for null and if it is null change it to an empty string otherwise pass through the current value. An empty st...

What issue are you having with #1? Both look fine to me at first glance. I'd also like to point out that your if tests in both cases are completely unnecessary, the use of NullToEmpty() by itself will get you the results you want without all those shenanigans: NullToEmpty(lkp_op.VENDOR_LID) The if-t...

I don't believe there is a macro for the ending time. However, you could certainly leverage the DSGetJobInfo() function with the (off the top of my head) DSJ.JOBLASTTIMESTAMP InfoType. A routine that establishes a handle to a job could get this for any job, and a Sequence could easily run the routin...

We both did. I said sorry I'm not quite sure what you think went on here, but there was no anger or issue with the wrong name being used. Heck, my reply was an obtuse reference to an old Cheech & Chong bit which is only funny if you're old like me. All I was saying in response to your "giv...