DSXchange

Thought that went without saying.

That's not a "workaround", at least not in my book.

Perhaps "we" should be having this conversation with prasad, could have sworn this was their thread.

So... the second comma delimited field is First and Middle. Pull that and then use Field again on that telling it is a space delimited string: 1=First and 2+=Middle. Now that won't always work but it should get you close enough so you can then identify the outliers.

Assign multiple people.

Have you been through Chapter 3. Improving performance of the Parallel Job Advanced Developer's Guide pdf? It's discussed there in a fair amount of detail.

So... this is resolved?

Then it sounds like you didn't hash on the correct columns... the keys in your target.

I don't think it would hurt to post it here. You'll need a screenshot / snippet of it uploaded to a file sharing site (like say Imgur) and then use the BBCode Image tags to link it in here.

Today's hint is "partitioning". Confirm that by running the job on a single node.

Isolation levels are about the locks that are (or are not) taken during the session.

Do you have the Server file metadata? Have you tried the 'Sync Parallel' option on it to populate the 'Parallel' tab with what your parallel job would need?

priyadarshikunal wrote:but why not update the same functions rather than using a new one?

Backwards compatibility.

Interesting and seems to be new as of June? From the video's description: The Migration Assistant is a new feature added to IBM Cognos Data Manager 10.2.1 to help customers migrate their Data Manager (DM) solutions to IBM InfoSphere DataStage (DS). It is envisaged that the tool is used as part of a ...

Aha! Told ya.