Database Reference
In-Depth Information
Executing Your Migration Package
You're now ready to test your SSIS package. In Visual Studio, 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 the UserDocs, Users, and Docs tables. Execution next goes to the first data flow, which queries
data from the local Docs table (source) and copies it to the TechBio database in the Docs table in SQL
Azure (destination). Execution then goes the second and third data flow tasks.
When execution is complete, all the tasks are green, as shown in Figure 5-15, letting you know that
they executed successfully. Any tasks that are yellow are currently executing. Red tasks are bad: that
means an error occurred during the execution of the task, regardless of whether the task was in the
control flow or data flow, and execution stops.
If your tasks are all green, 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 find
errors easily by looking for any line that starts with
Error:
toward the end of the list.
Errors you receive may be SSIS specific or SQL Azure specific. For example, did you define your
connections correctly? Microsoft makes testing connections very simple, and this doesn't mean the Test
Connection button. The Source Editors dialog—regardless if whether it's an OLE DB or ADO.NET
Editor—includes a Preview button that provides a small preview of your data, up to 200 rows. This
ensures that at least your source connection works correctly.
Verifying the Migration
When you have everything working and executing smoothly, in Visual Studio click the blue square
button on the toolbar to stop execution. Go back to SSMS, and query the three tables in your SQL Azure
instance to verify that data indeed copied successfully. As shown in Figure 5-16, you should see roughly
100 rows in the Users table, two rows in the Docs table, and two rows in the UserDocs table.
Figure 5-16.
Viewing migrated data in SSMS
