none
Script Component issues : SSIS 2014 to SSIS 2017 migration RRS feed

  • Question

  • Hi,

    I am trying to migrate our SSIS 2014 packages from SQL Server 2014 to 2017:

    The Extract packages have all been upgraded with the help of the SSIS Package Upgrade Wizard and manual (!) recompile of all .NET scripts in each package. The extract layer is running without any issues and pulling data from its sources.

    The TransformLoad layer packages are proving to be a major problem. It appears that Script Component is missing as can be seen from the first image below. Examining the source of one of the package, the Script Component version is still SQL Server v10 i.e. SQL Server 20108 R2 which was the original version of SQL Server used for this solution.

    Does anyone know why these script components are not being upgraded by the wizard? More importantly, is there a workaround without having to delete, add, edit every problem script component in every package?

    Tuesday, October 15, 2019 3:35 PM

Answers

  • Thanks Mona.

    The bottom line is that the SSIS Upgrade Wizard doesn't handle .NET scripts properly. I have spent the past 4 days flat out editing every single .NET component in every SSIS package.

    I hope you can tell the SSIS Wizard Developers that there are many SSIS users out there who have hit the same issue and I for one am not impressed with the wizard.

    • Marked as answer by amir tohidi Thursday, October 17, 2019 12:35 PM
    Thursday, October 17, 2019 12:35 PM

All replies

  • Hi Amir,

    perhaps the SSIS 2008 project was not properly upgraded to SSIS 2014 so you have to.

    I mean take the original 2008 project and upgrade to 2014 and then 2017. This may not be feasible I think, so you would need to drop and re-create these "stuck behind" components.


    Arthur

    MyBlog


    Twitter

    Tuesday, October 15, 2019 3:56 PM
    Moderator
  • The SSIS 2008 project was upgraded using the Upgrade Wizard. It was a pain also but it eventually worked.

    I think the upgrade wizard doesn't handle .NET script components at all well because it doesn't correct the DLL references and it does not compile the components either. It took me two days to recompile every single .NET script component in our Extract layers. I remember doing the same for the 2008 R2 to 2014 upgrade.

    There are others who have hit similar issues with the SSIS Upgrade Wizard. Not impressed.

    Tuesday, October 15, 2019 4:03 PM
  • Hi amir tohidi,

    I am glad to see that you have solved the issues.

    Yes, you should correct the DLL references and compile the script components again after upgrading.

    Please remember to click "Mark as Answer" the responses that resolved your issue.

    This can be beneficial to other community members reading this thread.

    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

    Wednesday, October 16, 2019 5:55 AM
  • Hi Mona,

    I have not fixed the issue. I managed to get the Extract layer packages to work but I still need a solution for  the TransformLoad layer packages issue as detailed in my original question above.

    Wednesday, October 16, 2019 6:05 AM
  • Hi amir tohidi,

    Please refer to the similar issue:

    SSIS Script component not Updating .NET framework after 2012 to 2017 Upgrade

    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 17, 2019 9:22 AM
  • Thanks Mona.

    The bottom line is that the SSIS Upgrade Wizard doesn't handle .NET scripts properly. I have spent the past 4 days flat out editing every single .NET component in every SSIS package.

    I hope you can tell the SSIS Wizard Developers that there are many SSIS users out there who have hit the same issue and I for one am not impressed with the wizard.

    • Marked as answer by amir tohidi Thursday, October 17, 2019 12:35 PM
    Thursday, October 17, 2019 12:35 PM
  • Hi amir tohidi,

    We will be glad to see that you can give feedback in the following link.

    https://feedback.azure.com/forums/908035-sql-server

    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 18, 2019 2:56 AM