Professional SQL Server™ 2005 Programming

19.4. Executing Packages

There are a few different ways to execute an SSIS package. We utilized one of these in something of test mode within the Dev Studio, but this is hardly how you are likely to run your packages on a day-to-day basis. The more typical methods of executing a package include:

• The Execute Package Utility — This is essentially an executable where you can specify the package you want to execute, set up any required parameters, and have the utility run it for you on demand.

• As a scheduled task using the SQL Server Agent — I'll talk more about the SQL Server Agent in Chapter 24, but for now, realize that executing an SSIS package is one of the many types of jobs that the agent understands. You can specify a package name and time and frequency with which to run it, and the SQL Server Agent will take care of it.

• From within a program — There is an entire object model supporting the notion of instantiating SSIS objects within your programs, setting properties for the packages, and executing them. This is fairly detailed stuff — so much so that Wrox has an entire book on the subject Professional SQL Server 2005 Integrations Services by Knight, et. al (Wiley, 2006). As such, we're going to consider it outside the scope of this book other than letting you know it's there for advanced study when you're ready.

19.4.1. Using the Execute Package Utility

The Execute Package Utility is a little program by the name of DTExecUI.exe. You can fire it up to specify settings and parameters ...