DSXchange

99 times out of 99 it's because of untrimmed character data on one side of the lookup or the other. As Arnd noted with his "HELLO" example. Ensure the metadata when created and used matches exactly.

OK, I'll byte... just how large is large?

ASU_ETL_DEV wrote:(like the automatic count that is shown at the end of a SQL DELETE against a relational database).

For the record, I have yet to use a relational database where a sql delete reported anything back automatically. Some may, but all certainly don't.

Take the service out of the picture. Copy the job and use a regular transformer as a stand-in, then check the performance. I'll wager the service itself is the bottle-neck.

Things like this make me smile:

Can you be more specific? What "values" are you talking about - adding new parameters to the set? Changing a default value? And can you clarify what exactly you mean by "reconfigure" here? Just want to ensure we're understanding the issue.

There isn't one. You can only do that from the Client GUI as far as I know. Did you mean to say "export" or is importing back the ultimate goal?

meet_deb85 wrote:Exact command is

Code: Select all

echo "X|`ls -l {file name for which counts are required}|wc -l|bc`"

What? There's absolutely no need to "list" anything and I have no idea what role you think the "binary calculator" is playing here.

Exactly what kind of changes are you making that require recompiles or 'reconfiguration' of the jobs that use them?

wittyme wrote:I need only the record 1 and 4.

As requested, you need to explain the why of needing "only the record 1 and 4", the rules that bring you to just those two out of the four. Looking just at the data, it is not exactly obvious, which is why people are asking you to throw them a bone.

Nicole wrote:Ok, and just to cover all bases - even if you shut down your machine - it will continue running without a problem.

Yes. As long as your machine is the client machine, of course.

Interesting... that wasn't the impression I've gotten from other posts here and never had a chance to actually play with it myself. Good to know. Is the 'compress' part optional? A 'standard' compression algorithm?

No, istool output isn't in XML format AFAIK and even if it was it's not the format you're expecting. Does this need to be done on the server side? You can do this using dscmdexport from any client pc.

What you'll find when you search is the need to sort your data properly and then assert that sorted order in the Aggregator. Then you'll find it can support pretty much any volume of data.