Beginning Microsoft SQL Server 2008 ... - S3 Tech Training

General
Figure 18-19
Many fields on this first dialog are fairly self-explanatory, but let’s pay particular attention to the Package
Source field. We can store SSIS packages in one of three places:
❑ The File System: This is what we did on our Import/Export Wizard package. This option is
really nice for mobility; you can easily save the package off and move it to another system.
❑ SQL Server: This model stores the package in SQL Server. Under this approach, your package
will be backed up whenever you back up your MSDB database (which is a system database in
every SQL Server installation).
❑ SSIS Package Store: This storage model provides the idea of an organized set of “folders”
where you can store your package along with other packages of the same general type or purpose.
The folders can be stored in either MSDB or the file system.
Configurations
SSIS allows you to define configurations for your packages. These are essentially a collection of settings
to be used, and you can actually combine more than one of them into a suite of settings.
Command Files
Chapter 18: Getting Integrated with Integration Services
These are batch files that you wish to run as part of your package. You can use these to do system-level
things such as copying files around to places you need them. (They will run under whatever account the
Integration Services Service is running under, so any required access on your network will need to be
granted to that account.)
559