Skip to content

catalog-deploy-packages.md

Latest commit

 

History

History
64 lines (43 loc) · 2.09 KB

catalog-deploy-packages.md

File metadata and controls

64 lines (43 loc) · 2.09 KB
title catalog.deploy_packages
description catalog.deploy_packages
author chugugrace
ms.author chugu
ms.date 03/04/2017
ms.service sql
ms.subservice integration-services
ms.topic reference

catalog.deploy_packages

[!INCLUDEsqlserver-ssis]

[!INCLUDE SQL Server]

Deploys one or more packages to a folder in the [!INCLUDEssISnoversion] catalog or updates an existing package that has been deployed previously.

Syntax

catalog.deploy_packages [ @folder_name = ] folder_name
    , [ @project_name = ] project_name
    , [ @packages_table = ] packages_table
    [, [ @operation_id OUTPUT = ] operation_id OUTPUT]

Arguments

[ @folder_name = ] folder_name
The name of the folder. The folder_name is nvarchar(128).

[ @project_name = ] project_name
The name of the project in the folder. The project_name is nvarchar(128).

[ @packages_table = ] packages_table
The binary contents of [!INCLUDEssISnoversion] package (.dtsx) file(s). The packages_table is [catalog].[Package_Table_Type]

[ @operation_id = ] operation_id
Returns the unique identifier for the deployment operation. The operation_id is bigint.

Return Code Value

0 (success)

Result Sets

None

Permissions

This stored procedure requires one of the following permissions:

  • CREATE_OBJECTS permissions on the project or MODIFY permissions on the package to update a package.

  • Membership to the ssis_admin database role

  • Membership to the sysadmin server role

Errors and Warnings

The following list describes some conditions that may cause this stored procedure to raise an error:

  • A parameter refers to an object that does not exist, a parameter tries to create an object that already exists, or a parameter is invalid in some other way.

  • The user does not have sufficient permissions