Re: Really want a answer, is there a mature way to access different data providers without performance lose? thanks!

From: Miha Markic [MVP C#] (miha)
Date: 02/17/04 

Date: Tue, 17 Feb 2004 11:59:40 +0100

Hi David,

One way is to create a factory pattern.
Depending on target datatabase you create appropriate instances and access
them through common interfaces. 

-- 
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com
"davidw" <davidw@affinisys.com> wrote in message
news:%23%231FruT9DHA.972@tk2msftngp13.phx.gbl...
> Thanks for reply.
>
> I did read the article you linked below recently, and a lot of other
> articles. But I still have no clear idea what is the suggestion way to
> develope a multi-datasource .NET program. Make it simple, if I want to
make
> I dll can support both SQL server and  mysql, what is the ideal way? OLEDB
> is much slower than sqlclient when connects to sql server, isn't it? ODBC
> uses another layer so it is more inefficient? what about interface
> IDBConnection,IDBCommand? I am not quite sure how they work, that is why I
> ask question here.
>
>
> "Cor" <non@non.com> wrote in message
> news:uvyjbVT9DHA.1112@tk2msftngp13.phx.gbl...
> > Hi David,
> >
> > You can use OleDB and ODBC also.
> >
> > In this newsgroup William Vaughn is more for ODBC, while others are for
> > OleDB.
> >
> > The performance from OleDB and ODBC is less than the performance form an
> > direct adapter as SqlClient.
> >
> > Have a look at this
> >
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconadonetproviders.asp
> >
> > I hope this helps?
> >
> > Cor
> >
> > > I always used sqlclient to access my sql server, recently, I want to
> > > develope some codes that can access data from other data providers,
like
> > > mysql, oracle. I found there are way to create universal data wrapper
by
> > > using adonet I?? interface, but I am still not sure if accessing sql
> > server
> > > with such way would comprise the performance a lot(compare to
> sqlclient).
> > > Does anyone could point to me a way to develope general data layer?
> >
> >
>
>

Relevant Pages

  • Re: Really want a answer, is there a mature way to access different data providers without performan
    ... I dll can support both SQL server and mysql, ... > You can use OleDB and ODBC also. ... > direct adapter as SqlClient. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Migrating to OLEDB
    ... In our tests the ODBC ... implementation outperforms the MSOLEDB interface by about 10%. ... OLEDB is almost complicated to the point of absurdity. ... > YCY> Specifically, SQL Server and Oracle providers are faster than ...
    (microsoft.public.data.odbc)
  • Re: Migrating to OLEDB
    ... In our tests the ODBC ... implementation outperforms the MSOLEDB interface by about 10%. ... OLEDB is almost complicated to the point of absurdity. ... > YCY> Specifically, SQL Server and Oracle providers are faster than ...
    (microsoft.public.data.oledb)
  • Re: Really want a answer, is there a mature way to access different data providers without performan
    ... You can use OleDB and ODBC also. ... > with such way would comprise the performance a lot(compare to sqlclient). ... > Does anyone could point to me a way to develope general data layer? ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Passing Parameter value in vb.net
    ... I would not use ODBC in dotNet anymore, use when you are able to SQLclient ... and when not OleDB. ... ODBC gives mostly a lot of troubles and after a while the one who tried goes ...
    (microsoft.public.dotnet.languages.vb)