- The People of the source table only use it to read (I have not update anything).
- The People of the destination table can not be deleted and refilled as its primary key is foreign key in other tables of the model. Thank you very much for your help from Argentina - the world's ass jeje -Hi Sebastian, Do you want to apply rules on tables (such as people on destination table cannot be deleted) ? for applying rules you can write Constraints and use Triggers on that table and fields in the database.
So we use same script as step 1 for this one as well. 3- Right click on OLE DB Source, choose Show Advanced Editor.Actions that I make and assumptions: - In the target table, I place all persons in the origin and still not in the destination.- In the target table, I need to update all those that have been modified at the origin.In the Advanced Editor window go to Input and Output Properties tab.Select the OLE DB Source Output, and change the Is Sorted Property to true.9- Add an OLE DB Destination and connect NEW RECORDS output to it.Set configuration for destination table and use columns with Source prefix in the column mapping of the OLE DB destination.We use this component to find only records that had a change in one of the values.So we compare equivalent source and destination columns to find non-match data.I don't recommend using Sort Transformation because it first load all records in memory and then start sorting them which cause performance issues and blocking.The best way is always sorting with order by clauses in source t-sql commands.