October 16, 2017 at 9:35 am
Has anyone experienced a difference between SQL driver SQLNCLI11.1 vs 10.1?
I inherited a complex SSIS package where I had to make minor changes (package loads data from 18 files to a SQL database).
The package works well with 10.1. But gives an error with Unicode to non-Unicode conversion with 11.1. I didn't want to change the mappings in the whole SSIS package for my change. So I'm planning to use 10.1 provider explicitly in the connection string.
Do any of you see any issue with this approach?
October 17, 2017 at 5:38 pm
SMNayak - Monday, October 16, 2017 9:35 AMHas anyone experienced a difference between SQL driver SQLNCLI11.1 vs 10.1?
I inherited a complex SSIS package where I had to make minor changes (package loads data from 18 files to a SQL database).
The package works well with 10.1. But gives an error with Unicode to non-Unicode conversion with 11.1. I didn't want to change the mappings in the whole SSIS package for my change. So I'm planning to use 10.1 provider explicitly in the connection string.
Do any of you see any issue with this approach?
Not sure if you are using OLE DB or ODBC but the following changes related to character conversions may be of interest to you:
ODBC Driver Behavior Change When Handling Character Conversions
In the short term no real issues abut eventually you'll need to address things. Or stop doing any upgrades. Forever 🙂
But that is often how people get burned - put off making those changes and then whatever they were using is no longer supported. Then you're in scramble mode when it stops working in production.
Sue
October 17, 2017 at 7:06 pm
Sue_H - Tuesday, October 17, 2017 5:38 PMSMNayak - Monday, October 16, 2017 9:35 AMHas anyone experienced a difference between SQL driver SQLNCLI11.1 vs 10.1?
I inherited a complex SSIS package where I had to make minor changes (package loads data from 18 files to a SQL database).
The package works well with 10.1. But gives an error with Unicode to non-Unicode conversion with 11.1. I didn't want to change the mappings in the whole SSIS package for my change. So I'm planning to use 10.1 provider explicitly in the connection string.
Do any of you see any issue with this approach?
Not sure if you are using OLE DB or ODBC but the following changes related to character conversions may be of interest to you:
ODBC Driver Behavior Change When Handling Character ConversionsIn the short term no real issues abut eventually you'll need to address things. Or stop doing any upgrades. Forever 🙂
But that is often how people get burned - put off making those changes and then whatever they were using is no longer supported. Then you're in scramble mode when it stops working in production.Sue
Thanks for your response, Sue. I am using OLEDB Native Client.
Usually, I use OLEDB native 11 by default for any development work. That's how I found this difference. Dev connection string (in SSIS config table) had explicit Provider=v10.1. Rest of the environments didn't have any provider mentioned. So, I assume SSIS chose to use the one from SSDT designer (which I use as v11.1 by default).
Apparently, Microsoft has changed how character conversions are done with new version of Native Client OLEDB.
October 17, 2017 at 8:59 pm
SMNayak - Tuesday, October 17, 2017 7:06 PMThanks for your response, Sue. I am using OLEDB Native Client.
Usually, I use OLEDB native 11 by default for any development work. That's how I found this difference. Dev connection string (in SSIS config table) had explicit Provider=v10.1. Rest of the environments didn't have any provider mentioned. So, I assume SSIS chose to use the one from SSDT designer (which I use as v11.1 by default).
Apparently, Microsoft has changed how character conversions are done with new version of Native Client OLEDB.
I'm guessing there could end up being some push from MS to get people to move to an updated driver. They reccently "undeprecated" the OLE DB driver for SQL Server and announced a new version will be released early 2018. It will support SQL Server 2012 - 2017.
Announcing the new release of OLE DB Driver for SQL Server
Sue
October 17, 2017 at 10:09 pm
Thank you, Sue. Had heard about the deprecating story earlier and was surprised :). Good they are retaining it even if its a newer version.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply