Splitsville for Oracle & .NET?

Microsoft today made official that the System.Data.OracleClient is being deprecated. In software terms this is code for “it’s not you, it’s me”. Breakups are never easy, but to ease the pain lets look as some of the facts:

It is easy to appreciate that deprecating an established component out of a platform as large as the .NET Framework is not an easy task. A long deprecation period such as this is exactly the right approach. It allows many people who may be depending on OracleClient to prepare, if not start migrating away from the OracleClient to a supported ADO.NET provider that has full throttle backing of a concrete roadmap and an ever expanding set of critical features.

If you’re seriously considering a migration from OracleClient, remember this might be an unexpected opportunity to retrofit your current or planned applications and upgrade your .NET to Oracle experience.

How could things change? Take performance upgrade as just one example:

I’d be interested in hearing other comments and thoughts on this topic too – comment below and let the debate begin!

Shares

2 Comments

  1. The Oracle / dot net breakup has been greatly exaggerated, unless Oracle deprecate their ODP.NET drivers too. Why was Oracle the only other db vendor to be honoured with a data provider included in the framework anyway? Makes no sense unless it was deliberately a bit crap to make Oracle look bad. There are plenty of excellent 3rd party ADO.NET providers anyway right? ;-) I can’t read the labels on your chart BTW. What is the x axis? Any chance of linking to a bigger version?
    Thanks,
    Michael.

    Reply

Submit a Comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>