DSXchange

Array size has no bearing on transactions size / commit points and cannot be set to zero. It is simply how many records are sent across the network at one time to the database.

Parallel or Server has no bearing on this conversation as either solution is equally valid for both. If you have a robust "job control" solution in place then there may be no need for Sequence jobs, perhaps only leveraging them for any situation that your job control cannot handle, if any.

Meaningless by itself. Post any other warning or fatal errors from the job's log.

The number after the flags?

You can't use a 'combo' action as it requires full metadata on each link. Use separate links, one for insert and one for update so you can have the appropriate metadata on each link. And use a reference hashed file to prequalify the action.

tippy1 wrote:I am using Enterprise 8.0 and comparing the error message of a server job vs a Px job in 8.0.

That's a completely different question than it seemed you were asking at first. Thankfully, Vincent has covered it.

What Craig is trying to say is that unless you dump the jobs to a dsx file and edit the dsx file there is no other "automated" way to change from UNIX to DOS line terminators. Hadn't even gotten to the "trying to say" part yet, Andy. :lol: But as you surmised was laying the grou...

Ok, was hoping for something other than that as that's similar to the approach already taken as a 'workaround'. Actually, the designer of the job converts any key null to the word "NULL" (these are string fields) when building the original hashed file, in the key expression during the refe...

This came up today and when searching here I found this unanswered post by Shane that I was hoping I could get... answered. :wink: Actually I am more interested in the treatment of a NULL in a HashFile where that NULL is part of the key. Will this be interpreted as a @NULL.STR when entered as oppose...

Hmmm... is a text editor considered "unauthorised packages or softwares"?

Sounds like you are loading duplicate values to a field that does not allow them. Stop doing that.

Ok, you should know the drill by now - what was the resolution?

Does "encrypt the data that is passing from source to target" mean you are looking for the data to be encrypted along the entire path of the job? I don't see that being feasible. However, if you mean in the job just before it is sent to the target then there are solutions either in the too...

De nada.

IsNull() is a function and you said you wanted to retain the value if not null so:

If IsNull(column) then 999 else column