DSXchange

I'm not sure the OE stage supports an 'anonymous block' like that. Perhaps try putting "END;" on a separate line?

You should consider moving it out to another area that does support it - ODBC as mentioned or the actual SP stage. Or script something to run it from the command line after job.

What I was thinking was along the lines of:
Where "Col1" and "01" change appropriately for each field to match their number.

Removing the users from the console would affect all projects, I would assume. Doesn't really sound like what you wanted, however.

Agreed.

nagarjuna wrote:yes you can increase and try that option

You know what the next question will be. If you are going to suggest something, best to also explain the 'how' of it while you're in there.

Wanting to set something at the environment level and being able to do so are two different things. To the best of my knowledge there is no such APT variable and no way to override the Array Size when sourcing from the OE stage. Happy to be proven wrong, however. As noted, you can when performing an...

Short answer? No.

Slightly longer answer... there's no ability to do the multiple levels of resolution (your 'eval') that you are looking for.

Not saying that there is no workaround of any kind, but nothing is popping into my head at the moment so just answering the question as asked.

Agreed. I usually want to gravitate to an 'after job' solution but this is better done before.

Nice.

For any "pick list" type parameters, like would help with "JobType", suggest you create that as a List parameter type. You can set the default to "none" to force a choice at runtime.

Transaction Size is equivalent to the commit level, hence my answer. The Array Size is only applicable to the Upsert method and is an optional 'sub-property' of the Insert SQL property.

First use Field() with '~' as the delimiter to get your three pieces and then Field() again on each piece with ':' as delimiter and take the second field from each.

Search here for "APT_ORAUPSERT" and you'll find the two environment variables that control that for the OE stage.

Or you may be able to read them in inside the Sequence job if the Sequence job itself doesn't need them, just the activities that it runs. For example, something like what was discussed here.

However. much cleaner to do this at the job control / script 'wrapper' level.

Make sure you have "Show link marking" enabled under the Diagram toolbar option... which is where 'relati' was going.