This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(201.6, 88%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMC%3C/text%3E%3C/svg%3E)
Hi,
I have to migrate SQL Server SSIS packages from a legacy machine onto a new one. The legacy machine used - as the IDE - Visual Studio 2017. These packages copied data from an existing 3rd-party system using their ODBC driver as the source connection. The provider of the ODBC driver has stated that it will support upto ODBC version 2.5, and not anything above (i.e. 3.0) and it will not upgrade the driver to do so in future. As the Visual Studio 2017 environment appeared to work, I am assuming that it must have issued ODBC 2.5 commands, and not 3.0. However, the newer environment (Visual Studio 2022) does not work, and according to the ODBC trace logs, it is issuing ODBC 3.0 commands.
As the driver will not support these commands, my question is whether it is possible to configure the OBDC Data Source in the SSIS Data Flow Task to issue only ODBC 2.5 commands, like it appeared to do with Visual Studio 2017.
I would be grateful if anyone can point me in the correct direction as how to achieve this task, as it's really quite confusing.
Thank you in advance.
C.
According to Wikipedia ODBC 3.0 was introduced in 1995. Good luck in finding any software produced in this millennium that supports ODBC 2.5!
Hopefully, the vendor is pulling your legs.
Hi Erland.
Thank you for the background information. Unfortunately, the vendor is not as they are wanting to move away from supporting the technology altogether.
Thank you.
Hi Eland,
Thank you for taking time to respond, and referencing the inception of ODBC 3.0. Unfortunately, the vendor has been direct in informing us that support beyond ODBC 2.5 will not be happening, as their plan is to move away from supporting their driver.
C.
Hi @Mr. C,
I do not think it is possible to use ODBC Version 2.5 in Visual Studio 2022.
You may try to deploy the SSIS package to sql server and run it from the new machine to see if it could run successfully.
Regards，
Zoe Hui
If the answer is helpful, please click "Accept Answer" and upvote it.
Hi ZoeHui,
Thank you for your response. Do you know whether it is possible in Visual Studio 2019?
The packages have been deployed to SQL Server, and they run fine from there. However, we are not able to make any changes to them in Visual Studio 2022, as attempting to do so throws a runtime error.
Kind regards,
C.
Hi @ZoeHui-MSFT A few of questions (if you don't mind me asking):
Thank you in advance,
C.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Or install Visual Studio 2017 - but this is not a long-term fix.
Well, using a driver which is no longer supported by the vendor, and apparently hasn't been for a long time is not a long-term solution in itself.
The only reasonable approach is to wrestle out the data in that antique data source into something else.
Hi Erland,
The driver technically is supported, but only for bug-fixes.
I agree that a reasonable approach would be to use a different manner to extract data, but that is not something that is not immediately available. I've been tasked with accomplishing this objective, so I am doing my best to do so with all known risks. It is far from ideal, and it somewhat of a battle, but I have to find a way.
Best wishes,
C.
I would say that staying on VS2017 is the best option for now, and you should see the obstacles with VS2022 that your organisation needs to give higher priority to re-architecture this solution - something they should have done long ago.
Thank you. It appears that Visual Studio 2017 doesn't seem to resolve the issue. So, possibly it is related to the SSDT extension versions??