DSXchange

Re-read Mike's post.

Validate then convert only if valid.

It has a single long field per record with many records or there is only a single long record per file?

I'm guessing that you should be able to do that, yes.

He just meant that when you associate a Multi-Instance job with a Job Activity stage, a new field should open up where you specify the Invocation ID. If you don't see that, close and re-open the Job Activity stage.

You don't need to "pass" it at all, you just reference it in the MI job and it will pick up the current version of the Invocation ID.

jwiles wrote:As is often requested for this forum...

Thank you James... saved me some typing.

Ask your SysAdmin.

As long as your logs are being stored in the 'traditional' repository, this post should give you a starting point at the very least.

Thank you Uncle Ken, wherever you are.

What 'derivation' do you have for the POC_ID column in the aggregator? In other words, what did you tell the aggregator to do with the field - group by it? Sum it?

That seems like a perfectly valid alternative.

There's a macro to reference the invocation id, DSJobInvocationID perhaps? I don't see why you couldn't use that for the table name.

Convert()

Look at the Date functions in the Parallel Job Developer's Guide, there should be something to get the current date, in pieces if needed.

From what I understand (but never tried) it is basically a 'compressed' dsx file and you can unzip it.

Which is exactly what they provide - a mechanism to make them dynamic.