Talend developer at a tech vendor with 501-1,000 employees
Vendor
Jul 20, 2017
The ADO provider is the standard data access code for Oracle from .NET:
Oracle Data Provider for .NET (ODP.NET) features optimized ADO.NET data access to the Oracle database. ODP.NET allows developers to take advantage of advanced Oracle database functionality, including
Real Application Clusters
XML DB
The Oracle Providers for ASP.NET you mention, is a specific release for helping with things like ASP.NET State Management, Membership and Roles:
ASP.NET provider developers will discover the Oracle Providers for ASP.NET are easy to learn and use as they share a common schema and API with existing ASP.NET providers. They integrate seamlessly with existing ASP.NET services and controls, just like other ASP.NET providers.
Oracle offers the following providers:
Membership Provider
Role Provider
Site Map Provider
Session State Provider...
Search for a product comparison in .NET Development Services
ODP.NET is better in case of working with multiple databases as well as in complicated cases. For simple cases or microsoft environments, you can go with ADO.NET
ADO.NET is simpler than ODP.NET. You should start with the first in case you have all microsoft based applications. In the minor case your company requirements are in big data terabytes you use Oracle ODP.NET as a adapter to .NET Common Language Runtime
Technical Consultant at a tech services company with 1,001-5,000 employees
Consultant
Aug 2, 2017
ODP.NET allows developers to take advantage of advanced Oracle database functionality, including Real Application Clusters, self-tuning statement cache, and fast connection failover.
Manager, Data Engineering Unit at a financial services firm with 1,001-5,000 employees
Real User
Jul 22, 2017
Talking about an oracle provider, Microsoft cannot possibly do a better job than than the owners of the database(Oracle). ODP is if feature-rich and supports a host of features that ADO simply doesn't (After all there is no point in going through all that for a competitor). ADO.NET is just fine for simple database operations. Check link below for a detailed comparison.
www.oracle.com/technetwork/topics/dotnet/index-154765.html
Associate (MS) at a tech services company with 501-1,000 employees
Real User
Top 20
Jul 22, 2017
Hello,
ADO.NET is better for some client in application development if you are start with Microsoft based application.
ADO.NET provider developed by Microsoft and its as a part of .NET Framework. Microsoft continue to provide support for issues in Oracle Client .NET Framework 4.0.
AND
ODP.NET is the .NET provider for Oracle database developed by Oracle.
Oracle provides .NET classes for accessing an Oracle databaMicrosoft is removing the Oracle data provider from its ADO.NET roadmap.
I heard that "Microsoft it decided discontinue its System.Data.OracleClient because a significant percentage of its MVPs tend to use alternative third-party offering are derived from ADO.NET base classes. This library is sometimes referred to as ODP.NET."
Is it correct ?
Software Developer at a media company with 1-10 employees
Vendor
Jul 20, 2017
.NET ORM COMPARISON
1. ENTITY FRAMEWORK – have used and I like it (especially entity framework core)
2. ADO.NET (have used a little and cant complain but cant prefer it entity framework)
3. ODP.NET (have never used)
.NET Development Services provide a robust framework for building scalable and high-performance applications. They cater to businesses of all sizes, offering seamless integration with various third-party tools and services.
Microsoft's .NET framework supports a wide range of programming languages, allowing developers to create versatile applications that cater to diverse business needs. It enables the development of web, mobile, desktop, and IoT applications, ensuring a unified...
The ADO provider is the standard data access code for Oracle from .NET:
Oracle Data Provider for .NET (ODP.NET) features optimized ADO.NET data access to the Oracle database. ODP.NET allows developers to take advantage of advanced Oracle database functionality, including
Real Application Clusters
XML DB
The Oracle Providers for ASP.NET you mention, is a specific release for helping with things like ASP.NET State Management, Membership and Roles:
ASP.NET provider developers will discover the Oracle Providers for ASP.NET are easy to learn and use as they share a common schema and API with existing ASP.NET providers. They integrate seamlessly with existing ASP.NET services and controls, just like other ASP.NET providers.
Oracle offers the following providers:
Membership Provider
Role Provider
Site Map Provider
Session State Provider...
ODP.NET is better in case of working with multiple databases as well as in complicated cases. For simple cases or microsoft environments, you can go with ADO.NET
ADO.NET is simpler than ODP.NET. You should start with the first in case you have all microsoft based applications. In the minor case your company requirements are in big data terabytes you use Oracle ODP.NET as a adapter to .NET Common Language Runtime
ODP.NET allows developers to take advantage of advanced Oracle database functionality, including Real Application Clusters, self-tuning statement cache, and fast connection failover.
Talking about an oracle provider, Microsoft cannot possibly do a better job than than the owners of the database(Oracle). ODP is if feature-rich and supports a host of features that ADO simply doesn't (After all there is no point in going through all that for a competitor). ADO.NET is just fine for simple database operations. Check link below for a detailed comparison.
www.oracle.com/technetwork/topics/dotnet/index-154765.html
Hello,
ADO.NET is better for some client in application development if you are start with Microsoft based application.
ADO.NET provider developed by Microsoft and its as a part of .NET Framework. Microsoft continue to provide support for issues in Oracle Client .NET Framework 4.0.
AND
ODP.NET is the .NET provider for Oracle database developed by Oracle.
Oracle provides .NET classes for accessing an Oracle databaMicrosoft is removing the Oracle data provider from its ADO.NET roadmap.
I heard that "Microsoft it decided discontinue its System.Data.OracleClient because a significant percentage of its MVPs tend to use alternative third-party offering are derived from ADO.NET base classes. This library is sometimes referred to as ODP.NET."
Is it correct ?
Thanks you all for your answers! I appreciate it and have have passed them along!
.NET ORM COMPARISON
1. ENTITY FRAMEWORK – have used and I like it (especially entity framework core)
2. ADO.NET (have used a little and cant complain but cant prefer it entity framework)
3. ODP.NET (have never used)
What is database? Oracle?