How to synchronize data from a source table to a destination table ?

[Anonymous]

Hy.
I'm not sure what I have to do to syncronize the data to a destination table from a source table (MSSQLSERVER).
The source table will has not to change.
On the destination table I have to do:
- Insert new records from source table
- Update the changes
- Delete the records deleted from source table
In particolar I'm was expecting an option on the Action property of the tMSSQLOutput component as "Update, Insert and Delete".
Do you have an example ?
Thank you and sorry for my english
Roby

[alevy]

I imagine you'd have to do this as:
1. Read the source
2. tReplicate
3. First replication to tMSSQLOutput component with Update or Insert option
4. Second replication to tMap as lookup with main flow from destination table with inner join rejects going to second tMSSQLOutput component with Delete option
If you want a combined action, you could put a feature request into the BugTracker.

[alevy]

Sorry, image was rejected on previous post.

[Anonymous]

Hello Netspa
If you are using TIS, it is easy to synchronize data from a source table to a destination table with CDC feature.
If you are using TOS, please see 11196. I showed a demo job.
Best regards
shong

[Anonymous]

Sorry, image was rejected on previous post.

Works ! Usefule using TOS components.
Thank you
Roby

[Anonymous]

If you are using TIS, it is easy to synchronize data from a source table to a destination table with CDC feature.

Yes I'm using TIS.
Do you have an example for this solution too ?
Thank you
Roby

[_AnonymousUser]

Hi.
I'm evaluating Talend Open Data and the first use case I tried to implement is data synchronization between two tables. Alevy, I've tried to replicate your job but I found no way to connect a tReplicate to a tMap the way you've shown in the image.
Could you please explain how to do it?
Thank you in advance,
-- Enrico

[Anonymous]

Sorry for the typo, I obviously meant Talend Open Studio. I'm running 4.2.3.

[Anonymous]

Ok,
Sorry but it seems it was the typical Windows application "close and restart" glitch...

[Anonymous]

I imagine you'd have to do this as:
1.  Read the source
2.  tReplicate
3.  First replication to tMSSQLOutput component with Update or Insert option
4.  Second replication to tMap as lookup with main flow from destination table with inner join rejects going to second tMSSQLOutput component with Delete option
If you want a combined action, you could put a feature request into the BugTracker.

Hi Alevy,
I know this is old, but I will be very grateful if you could upload the screenshot of this job design. I can't see it in the post and I'm struggling to accomplish this in TOS.
Thanks in advance.
Cheers,
Dela.