Comparing Third-Party Oracle.NET Providers

I am cleaning up an Oracle database application. Performance and ease of access are important in this application. It should go out of your way and allow you to receive data for free and without restrictions. However, it must be very fast. When it cannot be fast, it must be multithreaded so that it does not slow down the system.

All this aside, that’s what I found out. Microsoft has abandoned the System.Data.OracleClient namespace. It will be in .NET 4.0, but it will be noted with ObsoleteAttribute. Currently, I have replaced ODP.NET with Oracle (which turned out to be surprisingly painless), but, looking at other comments, I realized that I still have not been able to fulfill several design goals:

  • Perhaps I do not use the fastest provider.

  • I still cannot provide access to the SYSOPER account. I still do not quite understand why. It may be an encoding problem, but I'm at a dead end.

So here is my question for you guys.

What are the third-party alternatives to System.Data.OracleClient that you used, and what are their pros and cons?

+3
source share
2 answers

I used ODP.NET and I am pleased with that.

There were some downsides that went away with the latest version of the oracle instant client supporting odp.net.

+1
source

We have used ODP.NET since its first release and were very pleased with it. I have not used the following, but the fact that you can use them without installing the oracle client is attractive:

0

Source: https://habr.com/ru/post/1723031/


All Articles