DSXchange

Little tweak would do Sort the data based on the key column. Pass to Transformer. Default the stage variables to emptly string svNew = '' svOld = '' svSerialNp = 0 1. svNew: Col1[0,Index(Col1,'#',2)] 2. svSerialNo: If svNew = svOld Then svSerialNo Else KeyMgtGetNextValueConcurrent 3. svOld = svNew

Yeah... creates an issue when the &PH& gets full.
And RT_LOG, you can purge it with Admin level settings. Either Time based or run based.
Maintenance is all what, we talking about.

anbu wrote:Or Matches

Matches at Version 7?!
Anyway the topic is resolved

ETL server could be at higher end for few transformation and Metric calculations. And hence you might achieve the performance boost.
The trick is, you ll have to find the list of statements that has to be executed in ETL box and the ones that has be executed in DB box for better performance.

This is nice!!

Have you tried the option of 'Search' ?

That will be nice.

It is as synonymous to any other programing language. You have the Desing. Compile it using compiler. It generates the Executable. Executable can be executed to get the process flow. How to use this executable is of your choice. You can either execute it or keep it safe. :wink: To execute it you hav...

From the input, Remove the unwanted columns that are not required in the outut. Other than key if you are trying to extract same set of columns from both reference and Input stream, try to rename either one of the steam. Try to disable the Runtime column probagation. It might sometime try to get the...

Not sure how the space issue in Server side will affect the Client performance to a great extent. The connectivity between Server and Cleint is through network. Its obvious that if the data center is at very high distance for each data packet to reach easily, you ll get the lag during work. Did you ...

Try without Arguments. I read in one of the post that ODBC are not good in handling Procedures with Arguments.
Isnt Stored procedure stage working out for you?

Topic resolved? Do you like to mark it resolved?

Do a Inner join in the source with UPPER() and Trim function and then do a lookup in Datastage.
The first join in Database will ensure that, you get the Data from Source A only if it is present in Source B, and Vice versa. (You can change the join type if required.)

Does it have any OUT or Return?
Try with out Aruguments.

I was searching for something and replied to this post on reflex without noticing that the post is an year old.

Why not Truncating the table on Before job subroutine with a sqlplus call?

Pls try to aquire the membership, as it will be helpfull for you as well as for the forum.