Execution Patterns - SQL Server Integration Services Design Patterns - page 76

Note Appendix A contains information on building a serial SSIS framework that
was originally built for SSIS 2005. It works in SSIS 2014 if you use the package de-
ployment model.
Scheduling SSIS Package Execution
There are many commercially available software execution schedulers on the market.
They range from relatively simple to highly complex, allowing time- or event-based
execution. Many include metadata collection capabilities that track metrics such as ex-
ecution time. SQL Server Agent is a fairly robust job scheduling application included
with SQL Server. We will use SQL Server Agent to schedule the execution of our
demo package.
Caution Before proceeding, deploy the Chapter2 project to the SSIS Catalog. Doing
so will deploy Chapter2.dtsx and Parent.dtsx .
Scheduling an SSIS Package
Open SSMS and connect to an instance of SQL Server 2014. Open Object Explorer
and expand the SQL Server Agent node, if possible. Why might expanding the SQL
Server Agent node not be possible? By default, SQL Server Agent is installed as a
manual startup service.
Right-click the Jobs virtual folder and click New Job. When the New Job win-
dow displays, name the job Ch2 . Click on the Steps page and click the New button.
Name the new step Execute Chapter 2 Package and select SQL Server Integration
Services Package from the Type drop-down.
Select a Package Source from the drop-down. These are the options:
• SQL Server
• File system
• SSIS Package Store
• SSIS Catalog