OLDEDB drivers

Question

OLDEDB drivers

sqlfriend

SSC Guru

Points: 52781
More actions
March 21, 2024 at 4:57 pm

#4399606

How sql server OLDEBB or ODBC etc drivers intalled?
Are they installed from SSMS installation on the client?
Recently I have a new computer I installed SSMS 19.X version, and VS 2022, in visual studio 2022 SSIS project, when I create a connection manager the SQL native client driver is no longer available, I understand that is deprecated, and suggestion is to use MSOLEDBSQL.
But I also have some ssis package on SQL server 2019 version, which we cannot upgrade for now.
So I installed VS2019, but still the SQL native client is not there.
I just wondering how that was installed at the first place, is it installed through older version of SSMS?
Thanks

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Emperor100 SSCrazy Points: 2173 More actions · Answer 1

Try to download from this link:

https://learn.microsoft.com/en-us/sql/integration-services/azure-feature-pack-for-integration-services-ssis?view=sql-server-ver16

=======================================================================

sqlfriend SSC Guru Points: 52781 More actions · Answer 2

Thank you that is good to know about the Azure featured packs.

For my question particular I am interested how the drivers are installed, I think I figured it out, for server it is when install server, it has some shared features like client connectivity, for my computer, it could install from the SSMS, since I only installed the newest SSMS 19.x, so it did not install SQL native client.

Also find below, the first sentence shows me the SSMS installs drivers on client computer

The SQL Server Native Client (often abbreviated SNAC) has been removed from SQL Server 2022 (16.x) and SQL Server Management Studio 19 (SSMS). The SQL Server Native Client (SQLNCLI or SQLNCLI11) and the legacy Microsoft OLE DB Provider for SQL Server (SQLOLEDB) are not recommended for new application development. Switch to the new Microsoft OLE DB Driver (MSOLEDBSQL) for SQL Server or the latest Microsoft ODBC Driver for SQL Server going forward. For SQLNCLI that ships as a component of SQL Server Database Engine (versions 2012 through 2019), see this Support Lifecycle exception.

Jeff Moden SSC Guru Points: 1004323 More actions · Answer 3

I also download at least the latest version of the "ACE" driver/providers so that I don't need to go anywhere near SSIS just to import a spreadsheet.

https://www.microsoft.com/en-us/download/details.aspx?id=54920&irgwc=1

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

frederico_fonseca SSCoach Points: 16154 More actions · Answer 4

Jeff Moden wrote:

I also download at least the latest version of the "ACE" driver/providers so that I don't need to go anywhere near SSIS just to import a spreadsheet.
https://www.microsoft.com/en-us/download/details.aspx?id=54920&irgwc=1

even with SSIS the ACE driver should be used

sqlfriend SSC Guru Points: 52781 More actions · Answer 5

I did not download ACE on server, instead running the sql agent job in 32 bits, then it works.

But download that is good option too.

I don't want to download sql native client any more for newer SSIS.

This reply was modified 8 months ago by sqlfriend.