Re: ado vs oledb

Most mainstream SQL databases have "native" .NET providers using managed
code. These are supplied by the DBMS vendor or can be purchased from 3rd
parties like Data Direct. It's best to use these native providers before
attempting to use a generic OLEDB provider--if you care about performance.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
Between now and Nov. 6th 2006 you can sign up for a substantial discount.
Look for the "Early Bird" discount checkbox on the registration form...
-----------------------------------------------------------------------------------------------------------------------

"Jon Paal" <Jon[ nospam ]Paal @ everywhere dot com> wrote in message
news:uiF8pTT$GHA.1200@xxxxxxxxxxxxxxxxxxxxxxx
so, if I wanted to talk to sqLite through ADO, I would need "sqliteClient"
or I would need to get an oledb provider for SQLite ?

if I find an OleDB provider for SQLite then does it require installation
on the server for usage ?


"William (Bill) Vaughn" <billvaRemoveThis@xxxxxxxxxx> wrote in message
news:O3$qYYS$GHA.4356@xxxxxxxxxxxxxxxxxxxxxxx
ADO.NET is a data access interface that uses any number of .NET data
providers including SqlClient (to talk to SQL Server), SqlCe (to talk to
SQL Server Compact Edition), OracleClient (to talk to Oracle) and OSFA
providers like Odbc and OleDb which require ODBC drivers or OLEDB data
providers to talk to a variety of backends.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no
rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
Between now and Nov. 6th 2006 you can sign up for a substantial discount.
Look for the "Early Bird" discount checkbox on the registration form...
-----------------------------------------------------------------------------------------------------------------------

"Jon Paal" <Jon[ nospam ]Paal @ everywhere dot com> wrote in message
news:ODa5mDS$GHA.3860@xxxxxxxxxxxxxxxxxxxxxxx
what is the difference between oleDB and ADO.net provider ?







.

Relevant Pages

  • Re: OdbcConnection - parameter problem
    ... With the OLE DB providers you need to build a matching Parameters ... Hitchhiker's Guide to Visual Studio and SQL Server ... protected DbProviderFactory provider; ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: ASP.net hosting?
    ... manager access to the SQL databases - you must go through their interface. ... problem for writing in database on web. ... writing data back to database. ... The one I have seen are poor and also alot of providers ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ADSI
    ... providers for the integration with web application, ... "Joe Kaplan" wrote: ... used in SQL. ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: SqlDbType error message
    ... You should remove reference to System.Data.Common.dll as its functionality ... SQL Mobile providers. ... Files\Microsoft Visual Studio ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Apartment model OLEDB Provider
    ... > I've written an apartment model OLEDB provider that works fine with SQL ... I seem to recall having seen something about only in-process providers ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (microsoft.public.data.oledb)