Full circle for Microsoft database APIs as OLEDB for SQL Server is deprecated

Microsoft’s Eric Nelson has posted about how the OLEDB driver for SQL Server is being deprecated and will not be supported beyond “Denali”, the forthcoming version.

OLEDB was created to be the successor to ODBC – expanding the supported data sources/models to include things other than relational databases. Notably OLEDB was tightly tied to a Windows only technology (COM) whilst ODBC was not (Although we did try and take COM cross platform via partners)

ODBC never did get replaced. What actually happened is that ODBC remained the dominant of the two technologies for many scenarios – and became increasingly used on none Windows platforms and has become the de-facto industry standard for native relational data access.

ODBC was as I recall Microsoft’s first attempt at creating a universal database API.

The death of OLEDB will be slow, according to Nelson. The OLEDB driver for Denali will be supported for seven years following Denali’s release. He also says that OLEDB itself, as opposed to the SQL Server OLEDB driver, is not necessarily being deprecated; though frankly if Microsoft ceases supporting it with its own database I cannot see much future for it.

Note that ADO.NET, which to some extent replaced OLEDB, is not being deprecated. However ADO.NET is only usable from .NET applications. When you consider that Microsoft may be to some extent tilting away from .NET and towards native code, the deprecation of OLEDB becomes even more significant.

ODBC is not particularly easy to use in its raw form. However, you can wrap ODBC with, yes, an OLEDB provider or an ADO.NET provider; or you can wrap the whole lot in an object-relational framework such as Entity Framework.

One more chapter in the long, strange and tortuous history of Microsoft’s data APIs.

VN:F [1.9.18_1163]
Rate this post
Rating: 8.3/10 (3 votes cast)
Full circle for Microsoft database APIs as OLEDB for SQL Server is deprecated, 8.3 out of 10 based on 3 ratings

Related posts:

  1. Full circle at Microsoft: from the early days of .NET to the new Chakra JavaScript engine
  2. Amazon SimpleDB: a database server for the internet
  3. Where is your SQL Server CE Database?
  4. Moving a database from on-premise SQL Server to SQL Azure: some hassle
  5. Access Web App: at last a simple web database app builder from Microsoft

2 comments to Full circle for Microsoft database APIs as OLEDB for SQL Server is deprecated

  • This is kinda blowing my mind… and need to think it through. ie, did this have anything to do with ms’s retirement of the oracle client for .net? (i think it is oledb based right?). I haven’t used odbc in ages, i really kinda thought it had died out. sheesh.

  • Hello, I assumed that you are able to help me. I have a Microsoft SQL .ldf and .mdf file which I have to restore. Any opinions on how to do this? Take care