index > Windows Forms Designer > Why Separate SQL and OLEDB Commands

Why Separate SQL and OLEDB Commands

Hey Fellows,

Does anyone know the real reason why SQL and OLEDB database command objects were separated in .NET?

The thing is, I now have a MS Access application and uses OLEDB objects suchs as OLEDBDataReader, OLEDBCommand etc...

The data is now too large and I want to use MS SQL Server.

However it seems I have to rewrite the whole data access routines to achieve this.

Any ideas would be appreciated.

Thanks...

Computer Programmer

Damion Chambers Wednesday, January 21, 2009 1:10 PM

Hi Damion Chambers,

Do you mean your application based on MS Access will be upgraded to MS Sql Server?

First, Oledb provider does support MS Sql Server. The Microsoft OLE DB Provider for SQL Server provides an OLE DB interface to Microsoft® SQL Server�?2000 databases. Using the OLE DB Provider for SQL Server, SQL Server distributed queries can query data in remote instances of SQL Server.
http://msdn.microsoft.com/en-us/library/aa213282.aspx

You can take this article to know the difference between OleDBConnection and SqlConnection.
http://bytes.com/groups/net/111620-difference-between-oledbconnection-sqlconnection

If you need any detail help, please contact me.

Sincerely,
Kira Qian

Please mark the replies as answers if they help and unmark if they don't.