locked
SQL Server 2016 package deployment not working RRS feed

  • Question

  • Hi,

    Scenario:

    i create a ssis package in visual studio 2015. I set deployment model to package and the Solution Version to 2016.

    I connect to Integration Services on ServerA. Right Click on MSDB --> Import Package.

    After that i can see the package in the MSDB folder of Integration Services (just like it was in the versions before).

    First thing that is different:

    In the SQL Server in MSDB in table msdb.dbo.sysssispackagaes i cannot see the uploaded package. But in SQL Server 2012 and 2014 i can confirm that it was the case.

    As a main consequence i cannot call that package from within another SSIS Pcakage via Execute Package Task because the dropdown menu there cannot see the package because it looks on MSDB (sql server wise) instead of integration service.

    I think the inconsistency between what i see in integration services and in the sysssispackages table is a bug that leads to major problems.

    Can anybody confirm this bug or tell me more?

    Friday, June 24, 2016 11:21 AM

Answers

  • Hi there,

    The 2016 deployment is for SSIS 2016 only.

    Furthermore, the MSDB has been replaced with SSISDB since SSIS 2012.

    Deployments to MSDB are for maintenance jobs, not SSIS packages.

    You need to at the very least read about the deployments on MSDN where it says you deploy to a Catalog.


    Arthur

    MyBlog


    Twitter

    • Proposed as answer by Seif Wang Thursday, July 7, 2016 11:44 AM
    • Marked as answer by Eric__Zhang Sunday, July 10, 2016 12:26 PM
    Friday, June 24, 2016 1:20 PM