Is Microsoft retiring, discountinuing or deprecating SSIS OLEDB provider with ODBC?

There were announcements back in 2011 about Microsoft SQL Server OLEDB access going retire, now I heard it has been deprecating starting SQL SERVER 2014? However it is not apparent from MSDN pages linked below about depreciated features in SSIS 2012-2016. I also check deprecation pages for SQL SERVER 2012-2016 it has no mention there too.

2011年有关于Microsoft SQL Server OLEDB访问退出的公告,现在我听说它已经弃用了SQL SERVER 2014?但是,从下面链接的MSDN页面中可以看出SSIS 2012-2016中的折旧功能。我还检查了SQL SERVER 2012-2016的弃用页面,它也没有提及。

However, blog on MSDN seems persistent about it:

但是,MSDN上的博客似乎仍然坚持:

So my question are:

所以我的问题是:

Is Microsoft OLEDB is really being deprecated, if so from when? which version? Any support evidence?

Microsoft OLEDB是否真的被弃用,如果是这样的话?哪个版本?任何支持证据?

Are we suggesting we are going back to old days of ODBC?

我们是否建议我们回到过去的ODBC时代?

What are you using in your SSIS packages?

您在SSIS包中使用了什么?

Your experience with OLEDB to ODBC

您对OLEDB到ODBC的体验
- Deprecated Integration Services Features in SQL Server 2012
- Deprecated Integration Services Features in SQL Server 2014
- Deprecated Integration Services Features in SQL Server 2016
- Discontinued Integration Services Functionality in SQL Server 2012
- Discontinued Integration Services Functionality in SQL Server 2014
- Discontinued Integration Services Functionality in SQL Server 2016
- Breaking Changes to Integration Services Features in SQL Server 2012
- Breaking Changes to Integration Services Features in SQL Server 2014
- Breaking Changes to Integration Services Features in SQL Server 2016
- Behavior Changes to Integration Services Features in SQL Server 2012
- Behavior Changes to Integration Services Features in SQL Server 2014
- Behavior Changes to Integration Services Features in SQL Server 2016
- Deprecated Database Engine Features in SQL Server 2012
- Deprecated Database Engine Features in SQL Server 2014
- Deprecated Database Engine Features in SQL Server 2016
- Discontinued Database Engine Functionality in SQL Server 2012
- Discontinued Database Engine Functionality in SQL Server 2014
- Discontinued Database Engine Functionality in SQL Server 2016
- Behavior Changes to Database Engine Features in SQL Server 2012
- Behavior Changes to Database Engine Features in SQL Server 2014

1 个解决方案

#1

The deprecation of OLE DB is now deprecated. See Announcing the new release of OLE DB Driver for SQL Server

现在不推荐使用OLE DB的弃用。请参阅宣布SQL Server的OLE DB驱动程序的新版本

Previously, Microsoft announced deprecation of the Microsoft OLE DB Provider for SQL Server, part of the SQL Server Native Client (SNAC). At the time, this decision was made to try to provide more simplicity for the developer story around Windows native software development as we moved into the cloud era with Azure SQL Database, and to try to leverage the similarities of JDBC and ODBC for developers. However, during subsequent reviews it was determined that deprecation was a mistake because substantial scenarios within SQL Server still depend on OLE DB and changing those would break some existing customer scenarios.

此前,Microsoft宣布弃用SQL Server的Microsoft OLE DB Provider,它是SQL Server Native Client(SNAC)的一部分。当时,当我们使用Azure SQL数据库进入云时代时,我们决定尝试为Windows本机软件开发提供更简单的开发人员故事,并尝试为开发人员利用JDBC和ODBC的相似之处。但是,在后续审核期间,确定弃用是一个错误,因为SQL Server中的实质方案仍然依赖于OLE DB,并且更改这些方案会破坏一些现有的客户方案。

With this in mind, we have decided to undeprecate OLE DB and release a new version by the first quarter of calendar year 2018.

考虑到这一点,我们决定取消激活OLE DB并在2018年第一季度发布新版本。

This has now been released with one day to spare

现在已经有一天发布

#1