第三方的Oracle .NET提供的比较 [英] Comparison of 3rd Party Oracle .NET Providers

问题描述

我在清理Oracle数据库应用程序的过程。在本申请中，性能和易于访问的是最重要的关切。它有让自己的方式，让你的数据在一个自由和不羁的方式。虽然这样做，它必须的非常的快。当它不能快速，它必须被多线程，以便它不冻结了系统

I'm in the process of cleaning up an Oracle database application. In this application, performance and ease of access are paramount concerns. It has to get out of your way and let you get to the data in a free and uninhibited way. While doing that, it has to be very fast. When it can't be fast, it has to be multi-threaded so that it doesn't freeze up the system.

所有这一切的出路，这是我所学到的。微软已经去precated System.Data.OracleClient命名空间。这将是围绕在.NET 4.0中，但它会被打上ObsoleteAttribute。目前我已经换出来的ODP.NET从甲骨文（这竟然是出奇的无痛），但在审查其他的意见，我意识到，我仍然无法满足一些设计目标：

All of that out of the way, here's what I've learned. Microsoft has deprecated the System.Data.OracleClient namespace. It'll be around in .NET 4.0, but it'll be marked with ObsoleteAttribute. I've currently swapped it out for ODP.NET from Oracle (which turned out to be surprisingly painless), but in reviewing other comments, I realized that I was still failing to meet a few design goals:

1. 我使用的可能不是最快的供应商那里。

1. I might not be using the fastest provider out there.

我似乎仍不能提供访问SYSOPER帐户。我还没有完全制定出为什么呢。这可能是编码的问题，但我难倒。

I still can't seem to provide access to the SYSOPER account. I haven't quite worked out why, yet. That could be a coding issue, but I'm stumped.

因此​​，这里是我的问题了你们。

So here's my question for you guys.

什么是第三方替代System.Data.OracleClient的的您已经使用的，和他们有什么利弊？

What are the 3rd party alternatives to System.Data.OracleClient that you've used, and what are their pros and cons?

推荐答案

我用ODP.NET，我很满意。

I used ODP.NET and I'm satisfied with it.

有一些缺点，这是旷古的最后一个版本Oracle即时客户端支持odp.net的。

There were some cons, which are gone with the last version of oracle instant client supporting odp.net.

这篇关于第三方的Oracle .NET提供的比较的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！