Creating a Package in Business Intelligence Development Studio

In Business Intelligence Development Studio, you can create a new package by using one of the following methods:

• Use the package template that Integration Services includes.

• Copy an existing package.

• Use a custom package that you have designated as a template.

• Run the SQL Server Import and Export Wizard or the Integration Services Connections Project Wizard.

Using the Default Package Template

If you use the default Integration Services package template, the new package is empty. To add functionality to the package, you build the control flow and data flows, add connection managers, and implement other Integration Services features that the package requires. For more information, see Designing Package Control Flow, Designing Package Data Flow, Adding Connection Managers, and Adding Advanced Features to Packages.

To create a new package in SSIS Designer

• How to: Create or Delete a Package in Business Intelligence Development Studio

For a video that demonstrates how to create a basic package using the default package template, see Creating a Basic Package (SQL Server Video).

Using a Custom Template

To use custom packages as templates for creating new packages, you simply copy them to the DataTransformationItems folder. By default, this folder is in C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\ProjectItems\DataTransformationProject.

To create a new package by using a custom template

• How to: Save a Package as a Package Template

Copying an Existing Package

If existing packages include functionality that you want to reuse, you can build the control flow and data flows in the new package more quickly by copying and pasting objects from other packages. For more information about using copy and paste in Integration Services projects, see Reusing Package Objects.

If you create a new package by copying an existing package or by using a custom package as a template, the name and the GUID of the existing package are copied as well. You should update the name and the GUID of the new package to help differentiate it from the package from which it was copied. For example, if packages have the same GUID, it is more difficult to identify the package to which log data belongs. You can regenerate the GUID in the ID property and update the value of the Name property by using the Properties window in Business Intelligence Development Studio. For more information, see Setting Package Properties and dtutil Utility (SSIS Tool).

To create a new package by copying an existing package

• How to: Copy a Package in Business Intelligence Development Studio

Running a Wizard

Both the SQL Server Import and Export Wizard and the Integration Services Connections Project Wizard can create a package that sets up the connections that are required to access data sources and destinations. However, the package that the SQL Server Import and Export Wizard creates works with a single source and a single destination. The package that the Integration Services Connections Project Wizard creates works with multiple sources and destinations. For more information about these wizards and about which wizard to use, see Creating a Package by Running a Wizard.

Stay Up to Date with Integration Services For the latest downloads, articles, samples, and videos from Microsoft, as well as selected solutions from the community, visit the Integration Services page on MSDN or TechNet: Visit the Integration Services page on MSDN Visit the Integration Services page on TechNet For automatic notification of these updates, subscribe to the RSS feeds available on the page.

See Also

Concepts

Designing Packages in Business Intelligence Development Studio