Re: OLEDBCommand vs. SQLCommand
- From: "Marina Levit [MVP]" <someone@xxxxxxxxxx>
- Date: Wed, 6 Dec 2006 09:33:03 -0500
I think under certain circumstances, the SqlClient namespace classes are
going to provide you with better performance. They may also provide you with
more access to SQL Server specific functionality.
If your application does not need any of this functionality, and what you
are doing is not something that the SqlClient class can optimize for you,
then I suppose you can use OleDb so that you can swap out different types of
databases. If you are always using SQL Server though, then I see no reason
to not just always use the classes in SqlClient.
"Anil Gupte" <anil-list@xxxxxxxxxxx> wrote in message
news:uqMw73SGHHA.4116@xxxxxxxxxxxxxxxxxxxxxxx
When does one use one or the other? And why? I cannot imagine too many
innstances where you would not want to use SQL statements when you
communicating with a database - even on a read-only basis. Plus there is
the ODBCCommand class too - I understand that is an older implementation
and is not used in .Net much, correct?
Thanx for any clarifications and perhaps web links to discussion on this.
--
Anil Gupte
www.keeninc.net
www.icinema.com
.
- Follow-Ups:
- Re: OLEDBCommand vs. SQLCommand
- From: Anil Gupte
- Re: OLEDBCommand vs. SQLCommand
- References:
- OLEDBCommand vs. SQLCommand
- From: Anil Gupte
- OLEDBCommand vs. SQLCommand
- Prev by Date: Re: Which do you prefer?
- Next by Date: DLL returns a variant data type - how to convert and use in VB .NET
- Previous by thread: Re: OLEDBCommand vs. SQLCommand
- Next by thread: Re: OLEDBCommand vs. SQLCommand
- Index(es):
Relevant Pages
|
Loading