It is faster because it communicates with SQL Server through it's native 
language TDS. This bypasses the need for a Data Source. If you are using 
a Data source get rid of it and every thing should work fine if you are 
using the SqlClient classes. It doesn't need the OLEDB or ODBC Provider 
if you are working with SQL Server.

Kevin

> I have a little confusion about ADO.NET data providers.Its 
documentation 
s> ays
"> The SQL Server .NET Data Provider uses its own protocol to communicate 
w> ith SQL Server. It is lightweight and performs well because it is 
o> ptimized to access a SQL Server directly without adding an OLE DB or 
Open 
D> atabase Connectivity (ODBC) layer. The following illustration 
contrasts 
t> he SQL Server .NET Data Provider with the OLE DB .NET Data Provider. 
The 
O> LE DB .NET Data Provider communicates to an OLE DB data source through 
b> oth the OLE DB Service component, which provides connection pooling 
and 
t> ransaction services, and the OLE DB Provider for the data source."

> 
I> t means that OLEDB layer makes difference between SQLServer data 
provider 
a> nd OLE DB data provider.Then why when we use SQLconnection,its "Data 
Link 
p> roperties" shows "Microsoft OLEDB provider for SQL Server" on provider 
t> ab ?..Does it mean SQLconnection is using OLE DB layer?