1. Managing, Storing, and Executing DTS Packages

2. Managing Changing Package Elements
Connections
User names and passwords
Databases, servers, and file names
Tasks
Source and destination
Error file location

3. Disconnected Edit Functionality
Perform Changes Offline
View Read Only Properties
Change Read-Write Properties
Good for One Time Changes

4. Dynamic Properties Task
Typically Executes First in a Package
Dynamically Retrieves Values from an External Data Source
Assigns Retrieved Values to Various Package Properties at Runtime
Much More Flexible than Disconnected Edit

5. Dynamic Properties Task - Available Source Types
Initialization File - Supporting Values One Line in Length
Data File - Supporting Values Greater Than One Line
Query - Result Set Returning A Single Value
DTS Global Variable - Containing a Package Specific Value
Environment Variable - Containing a System Assigned Value
Constant - Containing a Static Value

6. Dynamic Properties Task Solutions
Assigning a Specific Package ID to the Execute Package Task
Managing the Source File of the Bulk Insert Task
Specifying the Executable for the Execute Process Task
Maintaining Connection Properties

7. Best Practices - Managing Package Connections
UNC Paths Instead of Drive Letters
Easy-to-Use Microsoft Data Link Files
Dynamic Properties Task Provides Flexibility
Offline, One Time Changes with Disconnected Edit

8. Storing Packages Meta Data Services Store common packages
Track metadata and data lineage
Visual Basic File
Build custom packages
Create prototypes for developers
Structured Storage Files
Move packages between servers
Use owner and user passwords
SQL Server Packages
Store common packages
Use owner and user passwords

9. Defining Package Executions
Package Execution Methods
Executing a package interactively
Using package execution utilities that are external to the Designer
Scheduling package executions
Package Execution Behavior
A package executes as a client application
A package uses system resources where it executes
A package must have valid connections and tasks
Runtime global variable assignments do not change package definition

10. Methods of Package Execution
Interactive Execution
DTS Package Designer
DTS Import / Export Wizard
Enterprise Manager
Package Execution Utilities
The dtsrun Command Prompt Utility
The DTS Run Windows Utility
Programmatically
Custom VB programs
Execute One Package from Another – Outer Packages
Execute Package Task

11. Creating Outer Packages
Executing Multiple Packages within a Single Package
Combining Modular Packages into Logical Workflows
Reusing Modular Packages in Different Workflows
Executing Packages in Parallel

12. Defining the Execute Package Task
Executing Inner Packages in an Outer Package
Assigning Global Variable Values from an Outer Package to an Inner Package
Participating in Package Transactions

13. Scheduling Packages Scheduling Packages in Enterprise Manager
Applies to SQL Server and Meta Data Services packages
Builds a SQL Server Agent job that you can edit
Scheduling Packages in the DTS Run Utility
Using a Custom SQL Server Agent Job
A Transact-SQL Job That Calls the dtsrun Utility
An Operating System Command Job That Calls the dtsrun Utility
An ActiveX Script Job That Performs a COM Automation Call

14. Troubleshooting Package Scheduling
Understanding Where the Package Runs
A package is a client application
A scheduled package executes under the security context of the owner of SQL Agent job
Understanding Who Owns the Package Job
Sysadmin owned jobs use SQL Server Agent
Non-sysadmin owned jobs use SQLAgentCmdExec
Identifying Potential Conflicts
File locations and database connections
COM components in ActiveX Scripts

15. Best Practices - Executing Packages
Using the Execute Package Task in Outer Packages
Executing Packages on the Computer Where You Want Them to Execute
Using Interactive Execution Methods During Development and Testing
Generating dtsrun Parameters by Using the DTS Run Utility
Verifying Owner Permissions of a Package Scheduling