Using the Extract file created in the Scenario 2 Extract
Process, you will specify an Insert Process that also inserts new
rows and updates existing rows in the destination database. You will
use the same destination tables used in Scenario 1, but the Scenario
2 Table Map will include a Column Map that transforms the inserted
data. Scenario 2 uses the remaining Insert Request settings from Scenario
1.
Open the Insert Request
This scenario builds on the Insert Request created in
Scenario 1. To begin, open that Insert Request.
- Click from
the main window.
- Double-click Insert
Request in
the Identifier list to display the list of
saved Insert Requests.
- Double-click the name
of the Insert Request saved
from Scenario 1.
Move populates the Insert
Request
Editor with the specifications saved in Scenario 1.
Rename the Insert Request
Before you modify the Insert Request for Scenario 2,
click to display the Save an Insert Request dialog
and create a copy of the original Insert Request.
Type
a new name to create a copy of the Insert Request for Scenario 2.
The original Insert Request will remain unchanged and modifications
for Scenario 2 will apply only to the new copy.
Type a new Description for
the Insert request, and specify the following parameters on the General tab:
- Extract File
- Enter
the name of the Extract File that contains
the data for Scenario 2. For this scenario, click the Last Extract
button
to
specify the last Extract File. If the Scenario 2 Extract File was
not the last Extract File created, use the Browse button
to locate the file.
- Control File
- Enter
the name of a Control File. You can use the
same Control File repeatedly. If a process executes successfully,
there is no particular reason to save the Control File.
- Table Map
- Similar
to Scenario 1, select the button labeled Local.
Edit the Table Map in the next step of this scenario.
- Process Options
- For
this scenario, select Update/Insert to
insert new rows and update existing rows in the specified destination
tables, as follows:
- If the primary key of a
row in the source data does
not match the primary key of a row in the destination table, the
row is inserted.
- If the primary
key of a row in the source data matches the
primary key of a row in the destination table, the row is updated.