Running in SQL Agent

These packages were designed to run together in a sequence. The CaseStudy_Load would be scheduled to run first. It may or may not have anything to process based on the time of day or the workload of the external payment processing vendors. The CaseStudy_Process will continue to perform the matching activity all throughout the day. When users have to manually identify an item, their identification can be stored either by updating the data in the dimension tables or in your lookup tables. The sample packages here would then use that information in the medium-confidence-level Data Flow on the next run of the job.

Figure 19-40 shows an example of the two jobs residing in the SQL Agent running in sequence.

Figure 19-40