Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, January 17, 2020 3:44 PM
How do I persuade VS 2019 to load the SSIS projects created in earlier versions? I'm simply told that they are 'incompatible'. There is also no sign of any related option in the configuration list for VS 2019.
EDIT: My previous Google searches didn't help, but I have just found some relevant threads on this forum.
All replies (5)
Monday, January 20, 2020 10:14 PM ✅Answered
I have a support contract with Microsoft and raised this problem with them. Today, I was advised that VS 2019 does not support SSIS projects created under any version of Visual Studio earlier than VS 2017. I was advised to install the latest update to SSDT for VS 2017, open a new SSIS project using VS 2017 and then import my older project (there is a wizard that made this easy).
I did this and VS 2019 is happy this updated version of my SSIS project.
After I did all this, I saw that the Properties page now looked like your example. I'm guessing that this might have been due to that SSDT update.
Friday, January 17, 2020 4:49 PM
This appeared to be the solution to my problem:
https://marketplace.visualstudio.com/items?itemName=SSIS.SqlServerIntegrationServicesProjects
I downloaded and installed this package and VS 2019 now includes the following new components:
- Microsoft BI Shared Components for Visual Studio
- Microsoft.VisualStudio.Tools. Applications
- SQL Server Integration Services Projects
Despite this update, VS 2019 still tells me that my SSIS projects are incompatible.
During the installation of the SQL Server Integration Services Projects package, I noticed a reference to SQL Server Management Studio 2014, but no references to a later version. I use SQL Server 2017, which can't be accessed properly via SSMS 2014 (I have to use SSMS 2018).
Any suggestions?
Monday, January 20, 2020 6:10 AM
Hi haggis999,
Welcome to MSDN forum.
If I understand correctly, you could try to change the “TargetServerVersion” from right-click project -> Properties -> Configuration Properties -> General -> Deployment Target Version -> “TargetServerVersion” like the screenshot below.
In addition, maybe this link: Changing the version of an SSIS package is helpful.
Hope this could help you and feel free to let us know if my suggestions are helpful or not.
Best Regards,
Tianyu
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 [email protected].
Monday, January 20, 2020 12:04 PM
Hi haggis999,
Welcome to MSDN forum.
If I understand correctly, you could try to change the “TargetServerVersion” from right-click project -> Properties -> Configuration Properties -> General -> Deployment Target Version -> “TargetServerVersion” like the screenshot below.
In addition, maybe this link: Changing the version of an SSIS package is helpful.
Hope this could help you and feel free to let us know if my suggestions are helpful or not.
Best Regards,
Tianyu
Hi Tianyu,
After opening my SSIS project in VS 2019 and then right-clicking on the project name, followed by selecting Properties, I get a dialogue box that looks rather different from your example. As you can see below, I don't have the configuration option you mentioned.
Tuesday, January 21, 2020 2:38 AM
Hello haggis999,
Thank you for your feedback.
Glad to hear that you could continue to work on your project, and we appreciate that you share us with your solution/troubleshooting. If you have any other questions about the usage of tools and editors in VS, feel free to contact us, we are here and happy to help you.
Have a nice day : )
Sincerely,
Tianyu
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 [email protected].