If it doesnt take a whole lot, its better to switch to SQLconnection.
Microsoft has lot of built-in features to use while using SQL connection. I am not sure if you can use LINQ to SQL with OLEDB connection.
SqlClient namespace classes implement a TDSParser which means they deal directly with the stream coming back from SQL; whereas OLEDB stuff runs through a more generic filter. SQL connection processes data lot faster than OLEDB if you are using SQL server.
One more thing, If your company bychance have plans to switch to any other database other than SQL(ORACLE) in future then probably you would want to keep up with OLEDB.
Marked as answer by techknackblogs on Mar 07, 2012 07:14 AM
Inayat Rasoo...
Participant
836 Points
285 Posts
Re: OledbConnection vs SqlConnection
Mar 06, 2012 02:18 PM|LINK
If it doesnt take a whole lot, its better to switch to SQLconnection.
Microsoft has lot of built-in features to use while using SQL connection. I am not sure if you can use LINQ to SQL with OLEDB connection.
SqlClient namespace classes implement a TDSParser which means they deal directly with the stream coming back from SQL; whereas OLEDB stuff runs through a more generic filter. SQL connection processes data lot faster than OLEDB if you are using SQL server.
One more thing, If your company bychance have plans to switch to any other database other than SQL(ORACLE) in future then probably you would want to keep up with OLEDB.