DSXchange

If you want 'step by step' be sure to read the XMLPACK_20_Designer.pdf manual in your Docs directory. It's all there.

Agreed, this annoys me as well.

From what I understand, it all changes under 8.0 - can someone verify?

There yah go.

On the patch issue, here is a post where both are mentioned. The 'crash patch' is not available on the Portal, you'll need to contact Support and arrange for them to make it available for you.

You need something to read the XML file - for Server a Folder stage is preferred.

Like that's going to help. Now they'll think you are Brian *and* the Father of Awk. Add a disclaimer that it's not your name.

kumar_s wrote:Yes, this routine wont be executed at all.

It will if also called in the Initial Value area, as I noted.

This is a known issue - Designer crashing working Sequence jobs - unrelated to SP2 and there is a separate patch for it. Search the forum, the specific patch is probably listed here somewhere.

Basically, you'll need to log on to the IIS Portal / eService website and download it.

I know no-one has asked for it, but thought I would throw in my two cents. I've said this before and I'll say it again. I would not consider any kind of 'hashing' algorithm suitable for surrogate keys. Period. If forced to choose between your two choices, I'd go MD5 over CRC32 or would push for one ...

Too slow.

Yes.

(1) Problem 1: I am still get the warning like this Seq_Test1..JobControl (@Execute_Command_46): Command /inbound/scripts/abc.sh did not finish OK, reply = '127' You will because your script sent a return code that is non-zero. All you did was turn off the fact that the job should automatically abo...

You have 'Automatically handle activities that fail' turned on and your command did not return a zero result - so it was considered to have failed.

Either turn off that option or read in the Help how to use two triggers to convince the Sequence job that you are handling the 'failure'.

I would suggest that you use your routine in the Initial Value column where the stage variable is defined to explicitly set the value to 'OK' when the job starts. Leave your other mechanism in place so that it is still used when rows actually do flow through the job.

In Server get the record count and Sort the data descending on the value in question. Constrain your output to the 'top 10%' of the records. ... I am facing problems in record count also as DSLINKINFo always returns 0 . How can we restrict the data to top 10 % . Get the record count before the job ...