Script Task – 2012 to 2014 Migration

Question

Script Task – 2012 to 2014 Migration

Phil Parkin

SSC Guru

Points: 246963
More actions
January 12, 2015 at 7:43 am

#296596

When you open an SSIS 2012 package in VS2013, the package is upgraded to the new 2014 format.
However, if the package contains any script tasks, they do not get upgraded. Instead, you receive a warning message: "Package contains a 2012 script task which must be migrated" (paraphrased)
I am assuming that this migration process is totally manual, but thought I'd check here to see whether that is the case. Am I right?
Thanks for your input.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Lempster SSCoach Points: 15651 More actions · Answer 1

I'm not sure about that Phil, but I would guess so. There are 3rd party tools that can assist...for a price obviously. About the package upgrading: it's not permanently upgraded unless you save the package or project containing the package. A good job too! 😉

Regards

Lempster

Stephanie Giovannini SSCertifiable Points: 7422 More actions · Answer 2

I'm having the same issue upgrading a package from SSIS 2012 to SSIS 2014. What exactly is the "totally manual" upgrade process? Re-create the script component? Edit the XML? I don't have a third-party tool available.

Phil Parkin SSC Guru Points: 246963 More actions · Answer 3

I've gone back to using SQL 2012 since writing the above post. However, I think it may be as simple as opening the script task for edit and then closing it again (clicking OK rather than Cancel, obviously).

At least, that's where I would start.

When 'saving' the script, if there are problems (perhaps because the .NET Framework version has changed), I would hope that SSDT would alert you to them.

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin

Stephanie Giovannini SSCertifiable Points: 7422 More actions · Answer 4

Apparently VS 2013 (SSDT 2014) still uses VS 2012 for scripts by design. So it looks like the script didn't migrate, but in reality, no migration is needed. More details are in the link below:

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/eda33b0e-12cd-4a29-a381-e1f7780c11b4/ssdtbi-for-vs2013-issues-with-vsta-script-transformations

Phil Parkin SSC Guru Points: 246963 More actions · Answer 5

Stephanie Giovannini (2/18/2016)
Apparently VS 2013 (SSDT 2014) still uses VS 2012 for scripts by design. So it looks like the script didn't migrate, but in reality, no migration is needed. More details are in the link below:
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/eda33b0e-12cd-4a29-a381-e1f7780c11b4/ssdtbi-for-vs2013-issues-with-vsta-script-transformations

Aha! Thanks for posting the link.

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin