DSXchange

Thanks jdmiceli and ArndW, thanks for your replies for helping me out. Here is what I have done. create table langdata (data1 nvarchar(2000)) sp_help langdata gives: data1 nvarchar no 4000 yes (n/a) (n/a) SQL_Latin1_General_CP1_CI_AS Then I did this: insert into langdata values (N'この種類のドキュメントでは、添付の保...

Hey Ray, Thanks for the quick answer. Although I could not read your post completely but got the point that the NLS setting for the SQL Server (or the character map) is inappropriate. But can you plz let me know what character map should I choose for the Sql server character set Latin1_General, beca...

Hi All, Good to see this forum, after long long time, active and happening. Here is the description of what I am trying to accomplish. Transferring data from Sql server stored in nvarchar columns (language sensitive, Japanese and english+may be some other language) to Oracle (UTF8 character set enab...

Hi All, Thanks for all the help you have provided so far. Ok, this is related with SCD2 dimension and I need your experience for designing the hierarchy table associated with a SCD2 dimension. The hierarchy is a recursive hierarchy. My question is what usual practice is followed for designing recurs...

We don't have Like in datastage instead use Matches. Take a look at the help for matching pattern creation.

Use Pivot stage, It would give you what you want with the duplicates, do a search on the handling duplicates, I am sure you will find lots of good posts on handling duplicates.

Got this from the manual: Setting Transport Block Size You can set the APT_AUTO_TRANSPORT_BLOCK_SIZE to True to have DataStage automatically calculate the block size for transferring data for transferring data internally as jobs run. The APT_DEFAULT_TRANSPORT_BLOCK_SIZE variable defines the block si...

Hey Kumar, I saw the tracing file that you are reffering to, but I am not really sure if any body can actually understand it and use it. Its huge and very difficult to make sense of what is really logged.

Did you get any chance any time to use it for such purposes?

UtilityRunJob('DSMyJob',link1.Col1|link1.Col2 ,50,50) is not correct.

It should be
UtilityRunJob('DSMyJob','Param1=' : link1.Col1 : '|' :'Param2=' : link1.Col2 ,50,50)

Where Param1, Param2 are the names of the parameter used in DSMyJob.

Yeah, it worked.

Does anyone know why it did not work with -wait and what is this APT_AUTO_TRANSPORT_BLOCK_SIZE?

In Version 8 you'll have a nifty utility to do that from what I hear.

That would be awesome

At times some or the other jobs are found missing in the project .

Or the reason could be corruption of the (index) of datastage specific hashed files (sometimes such cases happened with us also) like DS_JOBS etc. Perhaps something that can't be logged.

Looking at the topic heading Cascading lookup. I guess you mean something like Src Col1 to be Lookuped to Col1 (hash1) Col2 (hash1) to be lookuped to Col2(hash2) Cascading lookup is possible in the data stage, could be done in two ways 1st: In One transformer In TX1 Src Col1 to Hash1 Col1 and Hash C...

Why write a code when the same can be done through a simple Sequence Job The friendly GUI.

What about
creation_date = #YEAR# and creation_date > #Last Run Date#

#Last Run Date# can be another parameter passed from the Sequence, and you need to maintain it for all the partitions. You need to write routine(s) to write/fetch the last run date for each instance/partition.