Analysis phase - AWS Prescriptive Guidance

Analysis phase

Analyzing the information from the discovery phase helps you understand the patterns and design the target architecture better. Follow these pointers to improve the outcome of analysis:

  • The logging option at the package level logs events and captures runtime information for each component. Use custom logging so that you can configure log files to include additional information, such as execution IDs and other runtime values.

  • Redirect bad records to a different storage location for analysis, correction, and reprocessing.

  • Understand the data archival and purging strategies implemented in your on-premises SSIS environment.

  • Send alerts and notifications by using tasks that are included with SSIS (such as the Send Mail task) or custom scripts (such as the Script task).

  • Understand the behavior of transformations in scope to avoid corrupted data. For example, the Lookup transformation is an equi-join between two datasets, and its comparison is case-sensitive.

You can map each entry in the inventory to an estimated complexity, either in terms of duration (minutes or hours) or level (simple, medium, or complex). This expanded inventory, shown in the following table, is an outcome of the analysis phase.

SSIS ETL inventory mapped to estimated complexity, as a output of the analysis phase in migrations