DSXchange

This has been discussed quite a bit, which judicious searches would turn up. One such example:

viewtopic.php?t=112997

Which is exactly what I posted, example code and all.

Nice solution, Kryt0n.

Still don't really see the point and in my world would just hard-code it, but I guess that's just me.

Seems remarkably similar to this post:

viewtopic.php?t=125402

Why do you "need" to do this in a routine? Why not a simple Server job instead?

Which a search would have revealed... with caveats.

Interesting... then perhaps it doesn't actually support macros there. And if that's the case, you may need to hard-code the value in the Job Activity stage... something I don't really see a problem with. It's not like the value will ever change so why not hard-code it?

I haven't done anything like this, but I would certainly think that yes - for Step 5 you can use the DSJobName macro for part of the InvocationID as long as the 'job name' that you want is that of the Sequence job that is invoking the multi-instance job. Should be easy enough to build a small test s...

If that's the case, what it was that they "copied and pasted", I wonder?

First off, if this is really an Oracle DATE column, then you shouldn't be using the TO_TIMESTAMP() function but rather TO_DATE() instead. Dates in Oracle carry a time portion and a TIMESTAMP is a completely different datatype that takes the time down to a user selected microsecond level. You also on...

Time to mark the post as Resolved then it seems, using the green button at the top of the screen!

Sorry, it's all Greek to me.

(and here I thought 'ablative' was a type of armor good against lasers)

But the fact that the deletes 'can be seen' on the database side, which I take to mean they can be seen to be gone, would imply they have been committed and thus the Oracle part is done. Well... unless intermediate commits are being done and they only checked some.

Dammit, I even checked the spelling via Google and didn't notice it gave me the definition and quietly corrected the spelling at the same time without asking "Did you mean?". Guess it's a pretty common misspelling.

I don't believe we really know the 'context' this intends to be used in... other than from the command line, it seems. [shrug]