April 11, 2024 at 3:06 am
We have installed SQL 2022 & created the SSSIS catalog.
The visual studio is running on separate machine other than SSIS server.
The package is trying to pull the data from SQL server 2017 from a table from one database & inserting into the same SQL server 2017 on different database.
The package is deployed to SSISDB but it’s failing with the error Consider changing the provider in the connection string to MSOLEDBSQL or visit to find and install support for SQLNCLI11.
On SSIS server, SQL 2022 looks Microsoft removed the SQLNCLI11. Can I still download & install SQLNCLI11 on SQLServer 2022?
How can enforce the connection to use MSOLEDBSQL instead of SQLNCLI11?
April 11, 2024 at 6:00 pm
This link makes it sound like you can install the native client if you have apps that require it. https://learn.microsoft.com/en-us/sql/relational-databases/native-client/applications/installing-sql-server-native-client?view=sql-server-ver15
I tried but could not get Visual Studio 2017 to use MSOLEDBSQL. When I created a connection with OLEDB Provider for SQL Server it reverted to SQLNCLI11. In Visual Studio 2019 I was able to set the TargetServerVersion to SQL Server 2022 and I could then change existing SQLNCLI11 connections to use MSOLEDBSQL.
April 13, 2024 at 10:18 am
Thank you.
Somehow in Visual studio the target server version to SQL server 2022 is not able to see. It’s available up to SQL2019 only
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply