How to upgrade LastModifiedProductVersion in all packages

Question

I am migrating SSIS packages from SQL2016 to SQL2019 along with a number of extensions.

The LastModifiedProductVersion in the packages is used to locate the UpgradeMappings folder which points SSIS to the new extensions to be used.

However, I can't find a way to update this property in all packages without having to open each on individually, make a change and save the file. With a large number of projects and a lot of packages within each project, this is going to be quite a task.

Is there a way to update all packages in one go ("Upgrade All Packages" doesn't do this - that's just for the PackageFormatVersion property) and the TargetServerVersion for the project doesn't update this either.

Thanks.

Answer 1

Hi @Peter Bishop ,

I'm afraid that the LastModifiedProductVersion could not be automatically changed for all the packages.

The LastModifiedProductVersion is the version of Visual Studio which last modified the SSIS package.

Why do you want to upgrade it? If you do not meet any issue during the migration, you do not need to change it manually.

ssis-version

Regards，

Zoe

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi Zoe.

I may be making an incorrect association between this value and fixing the problem.

We are also upgrading extensions at the same time as SQL and the UpgradeMappings folder resides under the 150 tree. I made a (possibly incorrect) association that this value determined which SQL version tree would be searched.

If I deploy a package, unchanged, it fails trying to locate the extensions. But if I open a package, save it - no other changes on my part - and deploy it, it works.

Peter