Hi friends,
I want to know that what are advantages and disadvantages of Microsoft-provided data provider classes in ADO.NET?
Loading
Know the answer? Post it — somebody with the same question will find it here.
Sign in to answer this question
It is the same account you read, post and publish with — and you will come straight back to this page.
Jignesh TrivediPosted Feb 6, 2012, 10:55 PM
SQLServer.NET data provider is high-speed and robust, but requires SQL Server license purchased from Microsoft. OLE-DB.NET is universal for accessing other sources, like Oracle, DB2, Microsoft Access and Informix, but it is a .NET layer on top of OLE layer, so not the fastest thing in the world. ODBC.NET is a deprecated layer provided for backward compatibility to ODBC engines.
please refer
http://msdn.microsoft.com/en-us/library/904fck4k%28v=vs.71%29.aspx
hope this help.
VulpesPosted Feb 6, 2012, 11:34 AM
http://msdn.microsoft.com/en-us/library/3y0bb1zd(VS.80).aspx
You wouldn't expect Microsoft to list any disadvantages for their own product and the only real one is that it's purely a managed technology - it can't be used from unmanaged code.
At one time, there weren't many data providers (initially, just SQL Server, OleDb and Oracle). However, nowadays, there are third-party data providers for most of the commonly used relational databases.
Satyapriya NayakPosted Feb 6, 2012, 11:21 AM
.NET Framework Data Provider for OLE DB is universal for accessing other sources, like Oracle, DB2, Microsoft Access and Informix, but it's a .NET layer on top of OLEDB layer, Performance is not so faster.
.NET Framework Data Provider for SQL Server is used only for sql server database is high-speed and robust.Performance is faster.
.NET Framework Data Provider for Oracle is used only for Oracle database is high-speed and robust.Performance is faster.
Refer
http://msdn.microsoft.com/en-us/library/a6cd7c08.aspx
Thanks