DSXchange

Don't see a 'sequential file problem' here.

There's no 'right' way and there's always other ways possible. To me, the questions are: does this technique work for you? Is it efficient or at least efficient enough to not jeopardize your SLA? If so, then it's as right as any other solution.

I guess this performance problem is because of the key column is a string of 20 alphanumeric characters. No, it's all in the efficiency of your query. Compounded by the fact that it fires once for each record being processed. As noted, 7M records is NOT huge and should be easily handled by a hashed...

Right - guessing the OP wants to know how to avoid sending NULL values to a PK. However, given the vagueness of the question...

chulett wrote:please post the exact and complete error from the log.

Please. Also, what DSGuru posted goes without saying - the names must be the same, not should be. And on UNIX that means exactly the same, case and all: 'MyHash' != 'myHash'.

Not much you can do there, it's a full table scan regardless of the indexes, which would not be used. You sure you don't mean 'Group by A' ?

You are unable to create the hashed file, or to read it once you've created it? In any case, please post the exact and complete error from the log.

I'm curious... if there something special you are looking for? If so, you'd have to be more explicit what 'primary key null handling ' means to you so we can answer the right question. Or can we assume, like our friend has, that you just mean plain old null detection - in which case the IsNull() or ...

ray.wurlod wrote:You can use Fmt(InLink.TheString, "25T")

Ooooo... New trick for old dog. Thank you Master. :D

Yah, man - way more much betta.

Welcome! :D

Pretty much every stage out there has a 'View Data' button for that - except the XML stages. For that, you'll need direct access to your Server or work with someone who does to send the file(s) to you.

If PERIOD is a value in your User Variables stage, you can't refer to it just by name. You need to prepend the stage name to it as well. So if the stage was called Fred then: Fred.PERIOD = 'P11 ' Or Fred.PERIOD = 'P12 ' Or Fred.PERIOD = 'P10 ' Would be more appropriate. If you used the External Para...

'Invalid' expressions generally evalute to TRUE and so always trigger. Or more properly, anything that evaluates to '0' is FALSE and everything else is TRUE.

Can you post your actual code from each link from the Nested stage?

First off, that's not a proper expression. It would need to be: UtilityHashLookup('hshDateTime','1',2) = 'P01' OR UtilityHashLookup('hshDateTime','1',2) = 'P02' OR UtilityHashLookup('hshDateTime','1',2) = 'P03' to evaluate correctly, but that would run the utility three times...

So, I specified the option 'Ignore' as the Sort Order in the inputs tab of the Aggregator. Ignore is a dangerous option. Are you sure you truly have something more complex than can be declared as ascending or descending? Could it not be properly sorted so that it can be? Sure seems like it could be...

Then someone else here needs to step up and help you. Or your company needs to arrange for some 'official' Support for you. Sorry.