825
Chapter 31: Managing Data in Windows Azure SQL Database
31
FIGURE 31-17
Successfully executed SSIS Package.Errors you receive may be SSIS-specifi c or SQL Database specifi c. For example, did you
correctly defi ne your connections? Microsoft makes testing connections simple, and this
doesn’t mean the Test Connection button. The Source Editors dialog — regardless 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 correctly
works.Verifying the Migration
When you have everything working and executing smoothly, go back to SSMS, and query the
two tables in your your SQL Database instance. instance to verify that data indeed successfully
copied. As shown in Figure 31-18, you should see over 20,000 rows between the two tables.Other Cases to Consider
This example was simple; the source and destination tables were mirrors of each other,
including column names and data types. This made data migration easy. However, in some
cases the source and destination tables differ in column names and data types. There are
tasks that help with this, such as the Derived Column, Data Conversion, and Lookup
tasks. If you use these tasks and get errors, start by looking at these tasks to make sure
they aren’t the source of data-truncation or data-conversion errors.c31.indd 825c31.indd 825 7/31/2012 10:00:30 AM7/31/2012 10:00:30 AM
http://www.it-ebooks.info