How we can get unique records into one target table and
duplicate records into another target table??
Answers were Sorted based on User's Feedback
Answer / nag
Hi,
I think this scenario will help u.
Source - SQ Trans(2 Instances)-target(2 different targets)
In one of the Instances of SQ Trans write this Query:
select distinct <field name>......from <table name>;
Note:- It fetches only unique records.
In another Source instance write the following query:
select * from <table name> where rowid not in (select max
(rowid) from <table name> group by <field name>);
ex:- select * from emp where rowid not in (select max
(rowid) from emp group by ename);
Note:- It fetches only duplicate records.
then pass the fields to the targets(u should take different
targets).
I hope this will work.
Thanks and Regards,
Nag
Is This Answer Correct ? | 10 Yes | 3 No |
Answer / usha
1st method by using expression transformation by adding
variable ports.
2nd method by using dynamicLKP we can load UNIQ records to
one taget table and DUPLICATE records to other target table
newLKProw=1(Insert)
newlkprow=0(if there is no difference in associate ports)
UNIQ records
Is This Answer Correct ? | 10 Yes | 3 No |
Answer / hunny
Try This :
Source -> SQ -> Sorter(Sort by Ascending on Key) -> Aggregator(Group by key Column,var=count(key colmn) - > Router(var = 1) -> Unique Target and (var > 1 ) -> Duplicates.
Make sure the Datatype for Var is not String in this scenario else will encounter operands of ambigious types mismatch error.
Is This Answer Correct ? | 7 Yes | 0 No |
Answer / chetan
I/p
A
B
B
C
D
D
need to load A.C in one tgt and B,B,D,D in another target table.
SQ o/p should be given to aggregator. group by first column.create another port(v_count) with count(*).
SQ o/p should be passed to joiner to join aggr and SQ(source).
o/p looks like after joinning
A 1
B 2
B 2
C 1
D 2
D 2
use router to route v_count=1 and v_count=2 to different targets.
Is This Answer Correct ? | 6 Yes | 0 No |
Answer / naveen
Answer #3 is correct by Nag.
Addition to above second query for duplicate records, will
return unique records for each duplicate records.
if you need all duplicates records thn follow the below
query.
select * from emp
where empno in (select empno from emp group by empno having
count(empno)>1)
Regards,
Naveen
Is This Answer Correct ? | 6 Yes | 2 No |
Answer / bala
in router count(*)=1 for good record
count(*)>1 for duplicate record
Is This Answer Correct ? | 2 Yes | 0 No |
Answer / apoorva
question:
shouldn't the condition for unique_record be >= ??
Is This Answer Correct ? | 1 Yes | 0 No |
Answer / haaris
If the source is RDMS, then you can write analytic function in the select statement to assign count to each row. And use this count column to route the records to respective target.
If the source is a flat (this is generally asked in interviews), then you can use aggregator to assign count to each row after grouping based on the key and use joiner to join back to source records that way all the rows coming from the SQ will have respective counts. Use router to route them to respective targets.
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / amedela chandra sekhar
sq-->Aggregator-->Router-->target
select group by for port name empno
in aggregater t/r take 1 output port and give condition like
select group by for port name empno
varcount---->count(*)
connect this one router and in router take 2 groups and
give condition like
uniqe_record :varcount=1-----for unique
duplicate_record :varcount>1 ----for duplicate
and connect that groups to target.
u will get result.
Is This Answer Correct ? | 7 Yes | 10 No |
Answer / chandra
FIRST WE TAKE SORTER Tr ,BY USING THIS WE CAN RETRIEVE
UNIQUE RECORDS...NEXT
WE TAKE EXP Tr IN THAT INSERT NEW OUTPUT PORT ..,IN THE
OUTPUT PORT EXPRESSION WRITE COUNT FUNCTION AFTER THAT TAKE
FILTER Tr IN THAT PUT THE CONDITION AS
IIF(COUNT>1,TRUE,FALSE)THEN CONNECT TO TARGET......
SQ-->SORTr-->TARTr1(UNIQUE)
-->EXPTr-->FIL Tr-->TAR Tr2(DUPLICATES)
Is This Answer Correct ? | 17 Yes | 30 No |
My Source qualifier has empno, sal. Now my mapping is like SQ(EMPNO)->AGGR->EXP->TARGET SAL ------------>TARGET ? means only one source qualifier has 2 columns like empno, sal. connected to same target as shown in above mapping.Is this mapping valid or any issues are there if we design like this?
What does refresh system mean, and what are its distinctive choice?
what is session parameters?
Can anyone give some input on "Additional Concurrent Pipelines for Lookup Cache Creation" ? I know that this property is used to build caches in a mapping concurently. But which values should I set into this ( i.e. 1 or 2 or 3 or something else ) for concurrent cache building ?
what r the transformations that r not involved in mapplet?
How many numbers of sessions can one group in batches?
What is the function of aggregator transformation?
what are the transformations that restricts the partitioning of sessions?
How do you migrate data from one environment to another?
Where is metadata stored?
Hi friends I want to know about what r the dimensions in the banking porjects and genarally how many tables r in project ?
hw cn v elimate dublicate values from lookup without overriding sql?