DSXchange

keshav0307 wrote:i was having the same problem.
your project may corrupt anytime.
not sure, if REINDEX will help.
you may think of re creating the AUDIT logs also.

Please tell me what do u mean by 'REINDEX' and how will i do it?

the icon has changed like server job

Hi,

I had a parallel job. but some how that got converted to server job.
Is there any way to get back the original parallel job?

thanks

Is it enough if I partition the data on the joining keys before join? Or should I also sort the data on the joining keys? Also if I do not sort, will the join output be wrong?

why i mentioned to go for a separate sort stage as the volume increases is, in 'sort' stage there is an option called 'restricted memory usage' which by default is 20 MB. By increasing this memory, we can allocate more space for sorting which will increase the performance for higher volume of records.

It depends on the volume of records your job is handling. If the volume is less, you can perform hash partitioning in the 'merge' stage itself for both the input links on the keys you gonna merge and also check the perform sort option. But if the volume is in terms of millions or more, then have an ...

If you do a 'full outer join' if there is same value in both sides, only then they will join else the other value will be zero.

the result of 'full outer join' will be like

1 1
2 2
3 0

Can you please explain how the full outer join gives the expected result?

Are you mentioning any specific partitioning type in or before join?
If so, what partition and on which keys?

It is possible in a 'join' stage. For the first dataset you add one more dummy column with a dummy value say char(1) with value 'A' using 'column generator'. this new dummy column should have the same value for all the records from the first dataset. Now repeat the same thing for the other dataset. ...

What is happening when we mention method = sort / hash in aggregator stage? How do they differ?

could you tell me where to find the pdf 'ADVANCED PARALLEL JOB DEVELOPERS GUIDE '.

Nagesh, If there are any decimal type columns, then we can add an environmental variable 'APT_DECIMAL_INTERM_PRECISION' and set the value to 2. by default it is 38. by this we are limiting the internal calculations to use only 2 precision, which might speed up the job. PerterPol, It is enough to do ...

among the columns which you are aggregating, are there any decimal columns?

Hi,

In change capture stage properties, under output - columns tab,uncheck 'run time column propagation' and try running again.

hi,

In job already I am having a separate 'SORT' stage. Also I am sorting explicitly on the same keys on which I am partitioning in the same stage. Now should I check the perform sort option also for the sort to happen? In this scenario, checking and unchecking this option mean the same or different?