824
Part V: Enterprise Data Management
Put down the root beer, though, because you aren’t quite done. You still need to confi gure
the second data fl ow task to copy the data for the Employee table. Go back to the Control
Flow designer, connect the fi rst Data Flow task to the second Data Flow task, then confi g-
ure the second Data Flow task to pull data from the Employee table from the on-premises
AWMini database to the SQL Database Employee table. You don’t need to defi ne any new
connections so it should be quick.When you are fi nished, your Control Flow should look similar to Figure 31-16.FIGURE 31-16
Completed Control Flow.Executing Your Migration Package
You’re now ready to test your SSIS package. In SSDT, click the green arrow on the toolbar
to begin package execution. Execution starts at the Clear Data task — which, as you recall,
deletes all the data from fi rst the Employee table and then the Contact table. Execution
next goes to the fi rst data fl ow, which queries data from the local Contact table (source)
and copies it to the AWMini database in the Contact table in SQL Database (destination).
Execution then goes to the second data fl ow task.When execution is complete, all the tasks show a green check mark, as shown (albeit not
in green) in Figure 31-17, letting you know that they successfully executed. Any tasks that
have a yellow check mark are currently executing. Red check marks are bad: That means an
error occurred during the execution of the task, regardless of whether the task was in the
control fl ow or data fl ow, and execution stops.If your tasks have all green check marks, you can go back to your root beer. Otherwise, the
best place to start debugging is the Output window. All output, including errors, is written
to this window. You can easily fi nd errors by looking for any line toward the end of the list
that starts with Error:.c31.indd 824c31.indd 824 7/31/2012 10:00:29 AM7/31/2012 10:00:29 AM
http://www.it-ebooks.info