DSXchange

Actually it IS achievable, but only if you do the entire ETL job in code rather than stages. But I don't count that as "using DataStage".

If you attend the IBM DataStage Essentials class there is one page in the student guide that does attempt a summary of the differences between these three stage types. How about you make your own summary, based on reading the manual, and we can comment on that? You see, different things are importan...

It was tried. It was killed by Ascential's legal department.

Do you mean SAP R/3 or SAP BW ?

The answer to that question will determine which PACK (packaged application connectivity kit) you require.

Suman wrote:Server job now has to be converted to parallel job

Why?

If it isn't broken, don't fix it.

SQL Server Enterprise stage is only available on Windows platforms. No amount of documentation will change this situation. You will need to use the ODBC Enterprise stage.

This question looks suspiciously like this recent thread - are you on the same project?

Search the forum. This question has been asked, and answered, a gazillion times before.

Yes; if you can plan it you can implement it. JobA has unconditional trigger to JobB. JobB has conditional trigger to JobC and second conditional trigger (Failure) to abort handler. JobC has unconditional trigger to JobD. JobD has conditional (failure) trigger to abort handler. You can use the same ...

All of the derivations will generate NULL if there is NULL in the source. You need to do some detective work - perhaps using the debugger, perhaps using stage tracing - to determine in which line these NULL values are occurring. I would also ask you to demonstrate that what you are getting really is...

If they're unique enough letter pairs Index() may still do it for you. Something like: (Index(Convert(",", "", LetterPairs), MyLetterPair, 1) - 1) / 2 + 1 or, keeping the delimiters, (Index(LetterPairs, MyLetterPair, 1) - 1) / 3 + 1 Surely ...

Still waiting to hear from the original poster what the input format of the dates might be.

It's all a matter of representation and standards. Oracle tends not to follow the standards used by the rest of the world. For example, a timestamp with no fractional seconds is TIMESTAMP(19) most everywhere else. With milliseconds it's TIMESTAMP(23,3) and with microseconds it's TIMESTAMP(26,6). Dou...

Doesn't Search work for you?

The sqlldr utility requires only regular Oracle authentication. You can discover the answer to the "special characters" quesion on the forum. Indeed, it's answered by you in .a recent post!

For the example cited, INDEX would do the job. Index("ADCBJZ", InLink.TheChar, 1) Locate, Find and FindStr are, as you note, statements, and therefore not suitable for use in expressions unless encapsulated in routines. Otherwise the routine is not difficult. This one assumes a fie...