Microsoft Drops Its ADO.Net Oracle Provider

Microsoft made public a couple of days ago that they will be deprecating their ADO.Net Oracle Provider. This really should not be much of a shock as the number of people that connect to Oracle should be using the one that Oracle provides, Oracle Data Provider for .NET (ODP.NET). I heard about this while speaking to our local JSSUG group day before yesterday, as one of the attendees chimed up and mentioned it to the rest. No one really had an answer, so as I was trying to scarf down a slice of pizza, with my hand over my mouth, I mentioned that since ODP.Net was released, I have always used it while connecting to Oracle. Now my database of choice is SqlServer, however sometimes you gotta do what you gotta do. With that said, and without reading anything about it at that time(just saw this), I added that Microsoft probably felt it was time to let Oracle take that over to fry bigger and better fish. If Oracle did not have a superior provider, well then I might start digging deeper.

Turns out, if one has architected things to accommodate these types of changes, a conversion to Oracle Data Provider for .NET (ODP.NET) would not be a challenge. "Well Bayer what do you mean?", Glad you asked. Many times I share my passion for layered design pattern. Yeah I know that everyone has their opinions, however layering makes for a better approach in situations like this. Seperating out our data layer gives your application the opportunity to make changes like the ones others are wondering how many places MS Oracle provider touches. Without too much concern, MS's provider for Oracle is being depricated so there is still time to refactor what code needs to be changed.

Currently rated 1.5 by 2 people

  • Currently 1.5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Posted by: BayerWhite
Posted on: 6/19/2009 at 7:30 AM
Actions: E-mail | Kick it! | DZone it! |
Post Information: Permalink | Comments (77) | Post RSSRSS comment feed


Comments are closed