DSXchange

Usage Analysis is probably the first thing you need to do. Select each of the affected table definitions and use Usage Analysis to learn which jobs touch each of them. (If you have not been systematic with loading imported/saved table definitions in jobs, then Usage Analysis may not find all jobs; i...

We have a similar job where I am currently working. The explain plan suggests that grouping only has a lower cost than sorting only assuming that the join between the two tables is specified identically. (Our smaller table has 20,000 rows, not "just a few thousand". Our larger table has about six mi...

The amount of effort modifying active stage derivations probably makes working in the GUI the preferred approach, even if it does appear intensively manual.

I couldn't have put that any better. There is also a mindset difference; with Informatica one tends to design from the bottom up (take the data layouts and build an ETL structure on those), with DataStage one tends to design from the top down (draw the "big picture" and fill in the details).

Welcome aboard.

Yes, lots of us know. And a simple search of the forum would let you know also.

It does not happen automatically. You have to make decisions about what has to happen in the intervening active stages.

You don't need to worry. The outer loop's counter is not used. It just keeps incrementing by 1. Exit from the loop via a transfer to an activity beyond the EndLoop activity once it passes 6pm. Tip: also provide a "file read" or other mechanism for asking the outer loop to terminate prematurely.

Welcome aboard. There is a Slowly Changing Dimension stage that does all of the hard work for you. You do need to have set up a surrogate key generator of some kind. Read the documentation for the SCD stage, browse DSXchange for more information, and then post any specific questions that you have. C...

This really should be a separate thread! You can apply the UniSeq() function. If you get a valid integer result, then your map is correctly set. Otherwise it isn't. The ultimate answer is to get a copy of the Unicode reference manual from The Unicode Consortium - this contains all known characters t...

Yes you do. The reason is that adding a map has to edit a script that affects shared memory (in particular the segment that holds the maps), and to run a utility to "build" the map from data records contained in the NLS database. It's all in the DataStage NLS manual. Not sure why you get the message...

Welcome aboard.

There is a separate forum for questions about server jobs. Please post your question there.

You would do well to Search the forum first, as this question has been answered in the past. You may get your answer sooner.

In a job sequence. You're not the first to ask, so try searching the forum. It's a good source of ideas and techniques.

Disable operator combination so that you can find out where the error is occurring. Help us to help you. We simply can not (or at least will not) diagnose errors thrown by an arbitrary number of stages combined into the one process.

Umm... SAS and SAP are very different beasts!