Skip to content

create-packages-in-sql-server-data-tools.md

Latest commit

 

History

History
59 lines (39 loc) · 4.7 KB

create-packages-in-sql-server-data-tools.md

File metadata and controls

59 lines (39 loc) · 4.7 KB
title Create Packages in SQL Server Data Tools | Microsoft Docs
ms.custom
ms.date 03/06/2017
ms.prod sql-server-2014
ms.reviewer
ms.technology integration-services
ms.topic conceptual
helpviewer_keywords
SSIS packages, creating
Integration Services packages, creating
packages [Integration Services], creating
SQL Server Integration Services packages, creating
ms.assetid bb3c085b-1458-49fa-8348-6a76b6e97ea6
author janinezhang
ms.author janinez
manager craigg

Create Packages in SQL Server Data Tools

The packages that you create in [!INCLUDEssBIDevStudioFull] using [!INCLUDEssIS] Designer are saved to the file system. To save a package to [!INCLUDEssNoVersion] or to the package store, you need to save a copy of the package. For more information, see Save a Copy of a Package.

In [!INCLUDEssBIDevStudioFull], you can create a new package by using one of the following methods:

  • Use the package template that [!INCLUDEssISnoversion] includes.

  • Use 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 10.0\Common7\IDE\PrivateAssemblies\ProjectItems\DataTransformationProject.

  • Copy 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 [!INCLUDEssISnoversion] projects, see Reuse of 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 [!INCLUDEssBIDevStudioFull]. For more information, see Set Package Properties and dtutil Utility.

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

  • Run the [!INCLUDEssNoVersion] Import and Export Wizard

    The [!INCLUDEssNoVersion] Import and Export Wizard creates a complete package for a simple import or export. This wizard configures the connections, source, and destination, and adds any data transformations that are required to let you run the import or export immediately. You can optionally save the package to run it again later, or to refine and enhance the package in [!INCLUDEssBIDevStudio]. However, if you save the package, you must add the package to an existing [!INCLUDEssISnoversion] project before you can change the package or run the package in [!INCLUDEssBIDevStudio].

The following procedures describe how to create or delete a package in [!INCLUDEssBIDevStudioFull].

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

To create a package in SQL Server Data Tools using the Package Template

  1. In [!INCLUDEssBIDevStudioFull], open the [!INCLUDEssISnoversion] project in which you want to create a package.

  2. In Solution Explorer, right-click the SSIS Packages folder, and then click New SSIS Package.

  3. Optionally, add control flow, data flow tasks, and event handlers to the package. For more information, see Control Flow, Data Flow, and Integration Services (SSIS) Event Handlers.

  4. On the File menu, click Save Selected Items to save the new package.

    [!NOTE]
    You can save an empty package.