locked
HI Friends ! How we do Single package deployment to IS Catalog RRS feed

  • Question

  • HI Friends we have already Deployed SSIS Project to IS Catalog. Which Project has 4 packages. one package we had changed some tasks. So My requirement is We need to deploy that Edited package to IS catalog In 2012 is it possible.

    I am doing File system deployment Thanks for advance. Can you please give us your valuable Answers.

    • Moved by Fanny Liu Friday, December 13, 2013 8:27 AM more appropriate and better support in SSIS forum
    Wednesday, December 11, 2013 10:30 PM

Answers

  • Hi,

    The short answer is no.

    In SQL 2012, Integration Services supports two deployment models, the project deployment model and the package deployment model. The project deployment model enables us to deploy our projects to the SSISDB catalog on an instance of SQL Server. In project deployment model, a project is the unit of deployment which means that all the packages in the project will be deployed.

    If we right click on the \SSISDB\<FolderName>\Projects\ folder, we can see the “Import Packages…” option which allows us to import a single package. However, this method actually creates a new project to host the specified package (it can be one or more packages created in a SSIS project) and create an .ispac deployment file for the project, and then deploy the new project. If you choose this method to import the edited package to the existing folder in the SSISDB, it will overwrite the existing project folder and cause packages loss. So, the only way is to redeploy the whole SSIS project to overwrite the existing SSISDB project folder currently.

    If you have concerns on that, I would suggest you submitting a wish at https://connect.microsoft.com/sql.

    Connect site is a connection point between you and Microsoft, and ultimately the larger community. Your feedback enables Microsoft to make software and services the best that they can be, and you can learn about and contribute to exciting projects.

    Regards,


    Mike Yin
    TechNet Community Support

    • Marked as answer by Mike Yin Sunday, December 22, 2013 1:15 PM
    Sunday, December 15, 2013 1:21 PM
  • See this article by Matt Masson:
    http://www.mattmasson.com/2012/07/can-i-deploy-a-single-ssis-package-from-my-project-to-the-ssis-catalog/

    Please mark the post as answered if it answers your question | My SSIS Blog: http://microsoft-ssis.blogspot.com | Twitter

    • Marked as answer by Mike Yin Sunday, December 22, 2013 1:15 PM
    Sunday, December 15, 2013 3:11 PM

All replies

  • I have my doubts it is possible,  if you need to have them in the Catalog you need to deploy the entire project.

    Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/

    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting: Large scale of database and data cleansing
    Remote DBA Services: Improves MS SQL Database Performance
    SQL Server Integration Services: Business Intelligence

    Thursday, December 12, 2013 6:28 AM
  • we Able to deploy Entire project but we are not able to deploy Single package to IS Catalog. 

    Thanks for your Reply Uri Dimant
    • Edited by SQLCHERU Friday, December 13, 2013 3:40 PM
    Friday, December 13, 2013 3:39 PM
  • Hi,

    The short answer is no.

    In SQL 2012, Integration Services supports two deployment models, the project deployment model and the package deployment model. The project deployment model enables us to deploy our projects to the SSISDB catalog on an instance of SQL Server. In project deployment model, a project is the unit of deployment which means that all the packages in the project will be deployed.

    If we right click on the \SSISDB\<FolderName>\Projects\ folder, we can see the “Import Packages…” option which allows us to import a single package. However, this method actually creates a new project to host the specified package (it can be one or more packages created in a SSIS project) and create an .ispac deployment file for the project, and then deploy the new project. If you choose this method to import the edited package to the existing folder in the SSISDB, it will overwrite the existing project folder and cause packages loss. So, the only way is to redeploy the whole SSIS project to overwrite the existing SSISDB project folder currently.

    If you have concerns on that, I would suggest you submitting a wish at https://connect.microsoft.com/sql.

    Connect site is a connection point between you and Microsoft, and ultimately the larger community. Your feedback enables Microsoft to make software and services the best that they can be, and you can learn about and contribute to exciting projects.

    Regards,


    Mike Yin
    TechNet Community Support

    • Marked as answer by Mike Yin Sunday, December 22, 2013 1:15 PM
    Sunday, December 15, 2013 1:21 PM
  • See this article by Matt Masson:
    http://www.mattmasson.com/2012/07/can-i-deploy-a-single-ssis-package-from-my-project-to-the-ssis-catalog/

    Please mark the post as answered if it answers your question | My SSIS Blog: http://microsoft-ssis.blogspot.com | Twitter

    • Marked as answer by Mike Yin Sunday, December 22, 2013 1:15 PM
    Sunday, December 15, 2013 3:11 PM
  • Thank you very much MIKe Yin for your time reply to me 
    Monday, December 16, 2013 12:36 PM
  • Thanks for reply to me 

    Monday, December 16, 2013 12:37 PM