![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 33%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 73%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EST%3C/text%3E%3C/svg%3E)
Hope you are doing good! Thank you for reaching out. Please find the answer below.
From what you've described, it seems like your older installation has the necessary components for SQL Server 2019, while the new machine is missing some essential parts. This discrepancy could be because of a couple of reasons:
1.The SSDT 2017 installer on your new machine might not have included all the required packages that support SQL Server 2019.
2.The Microsoft Integration Services Projects extension on the new machine seems to be an outdated version (1.6) compared to the older machine (2.11), which might affect the availability of the SQL Server 2019 option.
Kindly follow the below steps to resolve the issue:
1.Repair or Modify Install: Run the SSDT 2017 standalone installer again on your new machine, and look for repair or modify options to ensure all components are correctly installed.
2.Update SSDT: Make sure you're using the latest version of SSDT. You may want to check Microsoft's documentation for any updates or patches you might have missed, here is the link SQL Server Data Tools - SQL Server Data Tools (SSDT) | Microsoft Learn
3. Install the Latest SSIS Extension for VS2017: Unfortunately, the Visual Studio Marketplace only lists the latest SSIS extension for VS2019 and newer, but there’s a workaround:
- Go to the SSIS extension GitHub releases page or search for archived versions of Microsoft Integration Services Projects compatible with VS2017.
- Look specifically for version 2.x of the extension. These versions include support for SQL Server 2019. Important: You may need to manually download and install the .vsix file for version 2.11 or similar.
4. Verify Installation: After installing the correct extension
- Check that the 150 folder appears under CommonExtensions\Microsoft\SSIS.
- Open your SSIS project and confirm that TargetServerVersion = SQL Server 2019 is now available.
5. Visual Studio 2019: If the above steps don't work, consider upgrading to Visual Studio 2019 or a later version if that’s an option for you. The newer versions have better support and might resolve the compatibility issue.
6. Check Folder Structure: Ensure that the folder structure in your installation aligns with the older machine, especially the folders you mentioned (140 and 150) under the SSIS path
If issue still persist after following all the steps, We’ll be happy to assist further if needed." Kindly mark the answer as accepted if the issue resolved".
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 21%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGH%3C/text%3E%3C/svg%3E)