DSXchange

Sorry... 'QS plug-in'? Are you asking about Quality Stage?

I can't believe this hasn't been covered before, but I can't get anything returned for a search on either 'before' or 'after'. Something seems to be broken. I couldn't either until I told it 'Exact Match'. Really don't think it should be working that way, but try that as a alternative. As mentioned...

elvishada wrote:have i still buy the bci except the datastage?

Yes. As Ray said, if you want to use ODBC outside of DataStage (like for BCI) then you must buy a full license.

can i use the odbc driver of 5 ?

No. At least, I don't believe so.

Why not take Ray's advice and do this in a DataStage job?

I'm curious if anyone is aware of any limitations in the use of the Pivot stage? One of my developers who makes heavy use of it is having problems trying to pivot one row into more than 64 rows. Now, don't ask me the whys or the wherefors. I'm not really sure why he needs to do what he is trying to ...

I can.

No probem. When you get a little deeper into it and have some specific questions, be sure to come back and ask them! Better to ask before than to fix later.

Technically, what is coming back to you in Output is a dynamic array that holds whatever is echoed to 'the screen'. Try changing your check to:


I don't believe you should need the 'trim', but it shouldn't hurt either.

Stage Variables are very handy and can be used to simplify things. They are evaluated (in order) before the derivations in your output links, so they can be used to cut down on the amount of work done in the Transformer. For example, a complex derivation that is used in multiple output links can be ...

UNIX is not like Windows, the current directory is not in your path by default. So, your command should be: cd /home/J76341/; ./new.sh #Output# You could also explicitly path the command: /home/J76341/new.sh #Output# And then do whatever directory changing you need to do inside the script.

Very interesting, Peter! I'll have to check it out when I get a chance and see how #2 compares to Uncle Ken's Magnum Opus, which we are currently using with great success.

There's really nothing magical about the 'settings' you would need. Your XML file is no different than any other ASCII file you'd be moving around via ftp. There should be a pdf document that describes the stage installed on your client machine and each field in the plugin should have help available...

Actually, it's the Sort stage that uses temp files, the Aggregator works in memory without landing anything. Unless things were different back in 5.x but I don't believe so. You can substantially reduce the amount of memory (and time) used by the Aggregator by presorting the data and asserting the s...

Besides, if you went with Informatica, you wouldn't have... well, us!

Hear Hear!

There's no context switching when calling a routine; the only overhead is determining its location (via the Catalog, or VOC file) and loading it into memory (this process is sometimes called "link snapping"); after that, the in-memory location is cached. Ah... thanks for the clarification. It was e...