Wrox Programmer Forums
|
.NET Framework 2.0 For discussion of the Microsoft .NET Framework 2.0.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the .NET Framework 2.0 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old December 13th, 2007, 10:07 AM
Registered User
 
Join Date: Dec 2007
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default help

hi everyone
i was questiontioned that why there is need for seperate sqlclient provider for ado.net already oledb provider works as generic provider which works for all connections
thanks
waiting for answer

 
Old December 14th, 2007, 02:14 AM
planoie's Avatar
Friend of Wrox
 
Join Date: Aug 2003
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

The native SQL .NET client is optimized for SQL Server. Yes, you can connect to a SQL server through ADO, but that adds the layer of ADO to the connection overhead. SqlClient connects directly to SQL and is therefore faster. It is likely there is also better support for more complex task involving transactions and the like that can be accomplished with optimized/direct connection.

-Peter









Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.