none
Upgrading SSIS Packages from 2008 to 2014 or 2016 RRS feed

  • Question

  • Greetings, we have a couple hundered SSIS packages on our standard ed 2008 R2 sql server created in BIDS 2008 which run on our Web1 SQL Server,the os is windows 2008 R2 standard. These packages are all run from SQL agent jobs, packages are saved on the file system, we uses xml config files to control the packages. We are preparing to upgrade this server (Web1) to SQL 2014 (because that is the licenses that were bought and they do not have SA). We are also looking to begin using SSRS in SQL Server 2016. This new SQL Server 2016 install (call it Web2) will initially be only used as an SSRS reporting server, but this will also eventually replace Web1 that houses our agent jobs/SSIS packages, so the SSIS packages will need to move to 2016. We have 2 other SQL 2008 R2 OLTP servers that replicate data to Web1, and will do the same for Web2. These other 2 OLTP server will also be upgraded to SQL 2014. My question is dealing with this upgrade and how to handle the SSIS upgrade, in the least number of conversions. I know I have to upgrade all the packages from 2008 to 2014 (upgrade wizard) but what would be better to go straight to 2016 for the SSIS upgrade or take the intermediate step to 2014? I have not used or worked with SSISDB, only bids and its use of Visual Studio for solutions/package management. I am also trying to determine what I need to download as far as SSDT/Visual studio to do this work. The SSDT links I have found are for 2017.  Appreciate any insight or suggestions on the approach
    Wednesday, October 9, 2019 3:24 PM

Answers

  • I am also trying to determine what I need to download as far as SSDT/Visual studio to do this work. The SSDT links I have found are for 2017.  Appreciate any insight or suggestions on the approach

    It is better to upgrade to the latest 2016 version (instead of having one intermediate conversion to 2014)

    You can use latest SSDT for VS2017 and while deploying it select the target version:


    Regards,
    Vaibhav

    • Marked as answer by Abeljdang Thursday, October 10, 2019 1:34 PM
    Thursday, October 10, 2019 7:45 AM

All replies

  • Hi Abeljdang,

    The following links will be helpful:

    Best Regards,

    Mona


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Thursday, October 10, 2019 2:02 AM
  • I am also trying to determine what I need to download as far as SSDT/Visual studio to do this work. The SSDT links I have found are for 2017.  Appreciate any insight or suggestions on the approach

    It is better to upgrade to the latest 2016 version (instead of having one intermediate conversion to 2014)

    You can use latest SSDT for VS2017 and while deploying it select the target version:


    Regards,
    Vaibhav

    • Marked as answer by Abeljdang Thursday, October 10, 2019 1:34 PM
    Thursday, October 10, 2019 7:45 AM
  • Thanks Mona, I had come across that link and it is helpful. 
    Thursday, October 10, 2019 1:33 PM
  • Hi Abeljdang,

    Could you please also mark my answer? Thank you.

    Best Regards,

    Mona


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Friday, October 11, 2019 1:09 AM