Here are some suggestions for me to code review the SSIS package, and if there are other better options for making bricks.
A. See if the best solution is used
1. Optimal view of the structure
2. Solution, package, task, build, parameter naming using easy-to-read naming method
3. Following the optimal design, optimization, adjustment scheme
B. Configuration
See if all of the configurations have been successful and are able to obtain the correct configuration information from the external and parent packages.
C. See if you can pass the following tests
1. The normal scene
- To view all table data/files that have been generated and are correct
- View all data in the table without being truncated or having unwanted spaces/characters
- Re-execute the package to see if there is duplicate data generation
2. The wrong scene
If there is an error stream, detect if the error stream is working properly
D. Log View
See if the generated log file contains all the debug information and can quickly determine the location of the error through the log information.
E. Publishing
Can you publish an SSIS package to a different test environment to work as you already have?
Code Review for SSIS package