DSXchange

If so, you will need the patch.

Probably true for a Windows based server installation, but how about UNIX?

The Tunables values are the default (not maximum) size to be used for hashed file cache - not hashed files. What you set in the Administrator is the default value; these can be overridden on a per-job basis using the job properties dialog. You're mixing up a couple of different things here. The def...

Was curious to see the actual job canvas, as circular dependancies are normally caught by the compiler.

User Defined SQL plus number of columns defined in stage not matching the parameter markers in the query = no descriptor for this position.

(Could not draw it accurately in the diagram) Then post a screen print of your job so it is accurate. There are many places offering free image hosting, upload a .bmp or .jpeg there and use the Img tags to include it in your post. Then maybe we'll be able to understand the structure and flow of you...

There's no way to eliminate 'the prompt' completely when you run the job manually - i.e. from the Director. It will always prompt for something, even if no parameters are defined in the job. You will always need to click 'Run' again in the dialogue box after clicking 'Run' on the menu. That's just H...

Are you using the actual Stored Procedure stage or some other mechanism?

What stages are you using? Generated or custom sql?

It's not arithmetic, it is a set operation, like a UNION or UNION ALL. Take the contents of the first set and remove any content that matches what's in the second set.

Not sure off the top of my head. I'd need to experiment and unfortunately I don't have time to do that right now. Perhaps later tonight I can, but right now anyone else is welcome to take a whack at this.

No, there's no 'demotion' in Server. All you can do is avoid generating them, if at all possible.

Another thing to try - export both jobs. Find the parameter block definition in the 'first job and replace what is in the 'second' job with that chunk. Re-import.

Save a copy of the original unadultered job in case you totally hork it up.

Which is exactly what the post I linked to states.

Direct access? Not sure what exactly that means. Can you not land this information and then process it? Write a job that extracts it from the database and writes it to a flat file, then process that flat file via the CFF stage. Or is that not direct enough access? There's no "NLS" involved in unpack...