ODBC vs Ole Db

My client is using a Sybase database. Should I use ODBC
or Ole Db with ADO.NET?

Thanks,
Todd

Miha
Fri Feb 06 03:48:34 CST 2004

Hi Todd,

Whichever suits you best.
I guess odbc one should be a bit faster.
Can't comment on differences between them though.

--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com

"Todd" <toddswygert@hotmail.com> wrote in message
news:ad7d01c3ec89$5ff85210$a101280a@phx.gbl...
>
> My client is using a Sybase database. Should I use ODBC
> or Ole Db with ADO.NET?
>
> Thanks,
> Todd

Todd
Fri Feb 06 13:31:44 CST 2004


OK, so other than speed no big advantages either way.
ODBC is it! Thank you for your post.

Todd

>-----Original Message-----
>Hi Todd,
>
>Whichever suits you best.
>I guess odbc one should be a bit faster.
>Can't comment on differences between them though.
>
>--
>Miha Markic [MVP C#] - RightHand .NET consulting &
software development
>miha at rthand com
>www.rthand.com
>
>"Todd" <toddswygert@hotmail.com> wrote in message
>news:ad7d01c3ec89$5ff85210$a101280a@phx.gbl...
>>
>> My client is using a Sybase database. Should I use
ODBC
>> or Ole Db with ADO.NET?
>>
>> Thanks,
>> Todd
>
>
>.
>

William
Fri Feb 06 15:59:53 CST 2004

It's a function of functionality as much as performance. The Odbc .NET Data
Provider is a "managed" provider while the OleDb provider is not (relies on
COM). However, the Sybase ODBC driver might not be as competent as the
Sybase OLE DB provider--just as the JET ODBC driver is a subset of the JET
OLE DB provider functionality. I suggest going to the Sybase site and seeing
what they recommend.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________

"Miha Markic [MVP C#]" <miha at rthand com> wrote in message
news:uBKLiZJ7DHA.3304@tk2msftngp13.phx.gbl...
> Hi Todd,
>
> Whichever suits you best.
> I guess odbc one should be a bit faster.
> Can't comment on differences between them though.
>
> --
> Miha Markic [MVP C#] - RightHand .NET consulting & software development
> miha at rthand com
> www.rthand.com
>
> "Todd" <toddswygert@hotmail.com> wrote in message
> news:ad7d01c3ec89$5ff85210$a101280a@phx.gbl...
> >
> > My client is using a Sybase database. Should I use ODBC
> > or Ole Db with ADO.NET?
> >
> > Thanks,
> > Todd
>
>

Miha
Mon Feb 09 02:06:46 CST 2004

Hi Bill,

"William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message
news:ONxuNyP7DHA.2404@TK2MSFTNGP12.phx.gbl...
> It's a function of functionality as much as performance. The Odbc .NET
Data
> Provider is a "managed" provider while the OleDb provider is not (relies
on
> COM).

It is a thin line though.
One relies on set of api while the other communicates through com.
I wouldn't say that the later is not a managed provider since both are only
wrappers.

--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com

William
Mon Feb 09 10:53:21 CST 2004

I didn't label them, the dev team at Microsoft did. My (informal) tests show
a dramatic (20%) difference in performance (Odbc over OleDb) when accessing
SQL Server. The SqlClient provider is even faster (once connected).


--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________

"Miha Markic [MVP C#]" <miha at rthand com> wrote in message
news:uAP3nOu7DHA.1716@TK2MSFTNGP10.phx.gbl...
> Hi Bill,
>
> "William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message
> news:ONxuNyP7DHA.2404@TK2MSFTNGP12.phx.gbl...
> > It's a function of functionality as much as performance. The Odbc .NET
> Data
> > Provider is a "managed" provider while the OleDb provider is not (relies
> on
> > COM).
>
> It is a thin line though.
> One relies on set of api while the other communicates through com.
> I wouldn't say that the later is not a managed provider since both are
only
> wrappers.
>
> --
> Miha Markic [MVP C#] - RightHand .NET consulting & software development
> miha at rthand com
> www.rthand.com
>
>

Miha
Tue Feb 10 02:21:02 CST 2004

Hi Bill,

"William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message
news:O91j60y7DHA.3880@tk2msftngp13.phx.gbl...
> I didn't label them, the dev team at Microsoft did.

I wonder what was the rationale behind.

My (informal) tests show
> a dramatic (20%) difference in performance (Odbc over OleDb) when
accessing
> SQL Server.

Interesting. Big boost indeed.

The SqlClient provider is even faster (once connected).

That was expected :)

--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com