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? 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.
SQL Server 2012 Connector and SQL Server Native Client 11.0 driver. For 64-bit connections in v9 or v10, download the X64 Package (sqlncli.msi). Nov 28, 2018 If you are planning to upgrade your ConfigMgr infrastructure to the latest 1810 release, plan for updating the SQL Server Native Client to support TLS 1.2 If the SQL Server native client isn't already updated, the prerequisite check will fail with below warning. The details are available in the ConfigMgrPrereq.log PRIMARY1; SQL Server.
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: 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. 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? Not sure if you are using OLE DB or ODBC but the following changes related to character conversions may be of interest to you: In the short term no real issues abut eventually you'll need to address things. Or stop doing any upgrades.
![Sql server native client 11.0 download Sql server native client 11.0 download](/uploads/1/2/5/5/125576022/256526708.png)
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.
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).
![Server Server](https://www.tishenko.com/content/images/2017/06/SP2016-Prerequisite-SQLNative-Download-Error.png)
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.
SQL Server Native Client 11.0 download for Windows 7 32 bit It is suppose to work. After searching an hour, MS claims it can be installed as part of the new SQL Server in one of the directories. Our development group doesn’t have access to the servers. Where can this installation (or dll) be located? Microsoft has made this extremely difficult. So difficult that there is an exploit phishing site that pretends to download the driver, but actually installs maleware. We are also running a SQL Server 2008 on a server.
Do we also need to upgrad it to this newer DLL? Would it help? Oledb-provider Download OLE DB Provider (SQL Server Native Client 11.0 OLE DB Provider) can be downloaded here (see next step).
2.aspx?id=29065 This downloads the following Text file: SQL Server 2012 Feature Pack Instructions: The links to the SQL Server 2012 Feature Pack components can be found in the “INSTRUCTIONS” section on the SQL Server 2012 Feature Pack page. – The “INSTRUCTIONS” section can be found about half way down the SQL Server 2012 Feature Pack page. – Once you navigate to the section please be certain to pick the appropriate component architecture for download.aspx?id=29065 – go to Install Instructions and read everything. Each is a download. Scroll about 46% down to Microsoft SQL Server connectivity Feature Pack Components.
Of Interest to this site: There is new Excel Add In for SQL Server Data Mining (several) ADO, OLEDB for DB2 (and others) JDBC, Direct stand-alone SQL Server Reporting, and my favorite: Microsoft® SQL Server® Migration Assistant that includes MS Access.aspx?id=28763 Microsoft SQL Server 2012 Native client e.g. SqlCmdLnUtils.msi is the 32 bit 47&clcid=0x409.