| Groups | Blog | Home |
dotnet ado.net : Can you use the OleDb classes for SQL Server?
Yes you can. OleDb is the old style way of abstracting database providers. The best way of doing abstraction is using stored procedures, as you can delegate sql queries to database, otherwise you end up with different version of queries for different RDBMSes. In addition, if you use .NET 2.0, it offers another way od specialization for different RDBMS via providers and factories: http://www.simple-talk.com/dotnet/.net-framework/ado.net-2.0-factory-classes/ Hoope this helps -- Milosz [quoted text, click to view] "Gustaf" wrote:
> I'm in a situation where the customer has an Oracle DB, and my developing platform runs a SQL Server DB. Ideally, I'd like to write the code, and then simply change the connection string at deployment time. So my question is: can I use the OleDb classes rather than the native SqlClient classes, to connect to SQL Server, and then later to Oracle? > > Gustaf
I have yet to see this work without a lot of compromises. While OLE DB or
ODBC can obfuscate the backend, the code you write to execute and manage the queries and the structures they return are very different for different providers. Again, a layered data object approach seems to be a better way to deal with this issue. -- ____________________________________ William (Bill) Vaughn Author, Mentor, Consultant Microsoft MVP INETA Speaker www.betav.com/blog/billva 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. __________________________________ Visit www.hitchhikerguides.net to get more information on my latest book: Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition) and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ----------------------------------------------------------------------------------------------------------------------- [quoted text, click to view] "Gustaf" <gustafl@algonet.se> wrote in message news:uiG0$PvvHHA.484@TK2MSFTNGP06.phx.gbl... > I'm in a situation where the customer has an Oracle DB, and my developing > platform runs a SQL Server DB. Ideally, I'd like to write the code, and > then simply change the connection string at deployment time. So my > question is: can I use the OleDb classes rather than the native SqlClient > classes, to connect to SQL Server, and then later to Oracle? > > Gustaf
No. Oracle uses different syntax, data flow and other methodologies in their
SPs. They are not compatible with SQL Server. I would write a data layer that uses the OracleClient .NET data provider to access Oracle. -- ____________________________________ William (Bill) Vaughn Author, Mentor, Consultant Microsoft MVP INETA Speaker www.betav.com/blog/billva 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. __________________________________ Visit www.hitchhikerguides.net to get more information on my latest book: Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition) and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ----------------------------------------------------------------------------------------------------------------------- [quoted text, click to view] "Gustaf" <gustafl@algonet.se> wrote in message news:umtbSDyvHHA.412@TK2MSFTNGP04.phx.gbl... > Milosz Skalecki [MCAD] wrote: > >> Yes you can. OleDb is the old style way of abstracting database >> providers. The best way of doing abstraction is using stored procedures, >> as you can delegate sql queries to database, otherwise you end up with >> different version of queries for different RDBMSes. > > I agree that it would be neat to just call a stored procedure for the > INSERT method I need. But a stored procedure I write for SQL Server can't > be moved directly to Oracle, can it? I know nothing about stored > procedures in Oracle. So I think I need to put the INSERT statment in the > C# code, or possibly in a config file. > >> In addition, if you use .NET 2.0, it offers another way od specialization >> for different RDBMS via providers and factories: >> http://www.simple-talk.com/dotnet/.net-framework/ado.net-2.0-factory-classes/ > > That's a good article. I was able to make use of the System.Data.SqlClient > provider, but the OleDb provider did not work. When opening the > connection, I get the useless error (type OleDbException): > > No error message available, result code: DB_E_ERRORSOCCURRED(0x80040E21). > > The app.config file currently looks like this: > > <?xml version="1.0" encoding="utf-8"?> > <configuration> > <appSettings> > <add key="provider" value="System.Data.OleDb"/> > <add key="connectionString" value="Provider=SQLOLEDB;Data > Source=.;Initial > Catalog=MyCompany;Integrated Security=true;User Instance=True"/> > </appSettings> > </configuration> > > The solution would still be very useful, if I can just change > "System.Data.SqlClient" to "System.Data.OracleClient" at deployment. > > Gustaf
Howdy,
I didn't mean using the same stored procedures for different RDBMSes. I meant you can use OleDb to call SPs (which is pretty much the same ADO.NET code), but you would have to implement them differently for each RDBMS. In addition, real life applications are much more advanced than simple SELECT, INSERT, UPDATE statements, and that's why i mentioned you would end up with different versions of queries for different RDBMS. I definitely agree with William it's better to use abstraction in the code such as providers and i mention about in my previous post. Best regards -- Milosz [quoted text, click to view] "Gustaf" wrote:
> Milosz Skalecki [MCAD] wrote: > > > Yes you can. OleDb is the old style way of abstracting database providers. > > The best way of doing abstraction is using stored procedures, as you can > > delegate sql queries to database, otherwise you end up with different version > > of queries for different RDBMSes. > > I agree that it would be neat to just call a stored procedure for the INSERT method I need. But a stored procedure I write for SQL Server can't be moved directly to Oracle, can it? I know nothing about stored procedures in Oracle. So I think I need to put the INSERT statment in the C# code, or possibly in a config file. > > > In addition, if you use .NET 2.0, it offers > > another way od specialization for different RDBMS via providers and factories: > > http://www.simple-talk.com/dotnet/.net-framework/ado.net-2.0-factory-classes/ > > That's a good article. I was able to make use of the System.Data.SqlClient provider, but the OleDb provider did not work. When opening the connection, I get the useless error (type OleDbException): > > No error message available, result code: DB_E_ERRORSOCCURRED(0x80040E21). > > The app.config file currently looks like this: > > <?xml version="1.0" encoding="utf-8"?> > <configuration> > <appSettings> > <add key="provider" value="System.Data.OleDb"/> > <add key="connectionString" value="Provider=SQLOLEDB;Data Source=.;Initial > Catalog=MyCompany;Integrated Security=true;User Instance=True"/> > </appSettings> > </configuration> > > The solution would still be very useful, if I can just change "System.Data.SqlClient" to "System.Data.OracleClient" at deployment. > > Gustaf
I'm in a situation where the customer has an Oracle DB, and my developing platform runs a SQL Server DB. Ideally, I'd like to write the code, and then simply change the connection string at deployment time. So my question is: can I use the OleDb classes rather than the native SqlClient classes, to connect to SQL Server, and then later to Oracle?
[quoted text, click to view]
Milosz Skalecki [MCAD] wrote: > Yes you can. OleDb is the old style way of abstracting database providers. > The best way of doing abstraction is using stored procedures, as you can > delegate sql queries to database, otherwise you end up with different version > of queries for different RDBMSes. I agree that it would be neat to just call a stored procedure for the INSERT method I need. But a stored procedure I write for SQL Server can't be moved directly to Oracle, can it? I know nothing about stored procedures in Oracle. So I think I need to put the INSERT statment in the C# code, or possibly in a config file. [quoted text, click to view] > In addition, if you use .NET 2.0, it offers > another way od specialization for different RDBMS via providers and factories: > http://www.simple-talk.com/dotnet/.net-framework/ado.net-2.0-factory-classes/ That's a good article. I was able to make use of the System.Data.SqlClient provider, but the OleDb provider did not work. When opening the connection, I get the useless error (type OleDbException): No error message available, result code: DB_E_ERRORSOCCURRED(0x80040E21). The app.config file currently looks like this: <?xml version="1.0" encoding="utf-8"?> <configuration> <appSettings> <add key="provider" value="System.Data.OleDb"/> <add key="connectionString" value="Provider=SQLOLEDB;Data Source=.;Initial Catalog=MyCompany;Integrated Security=true;User Instance=True"/> </appSettings> </configuration> The solution would still be very useful, if I can just change "System.Data.SqlClient" to "System.Data.OracleClient" at deployment.
While both can be called in pretty much the same way, the way resultsets and
returned parameters and multiple rowsets are handled is very different. -- ____________________________________ William (Bill) Vaughn Author, Mentor, Consultant Microsoft MVP INETA Speaker www.betav.com/blog/billva 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. __________________________________ Visit www.hitchhikerguides.net to get more information on my latest book: Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition) and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ----------------------------------------------------------------------------------------------------------------------- [quoted text, click to view] "Milosz Skalecki [MCAD]" <mily242@DONTLIKESPAMwp.pl> wrote in message news:EA07F097-A5AC-4BF6-84B5-EE8AE1CE76F5@microsoft.com... > Howdy, > > I didn't mean using the same stored procedures for different RDBMSes. I > meant you can use OleDb to call SPs (which is pretty much the same ADO.NET > code), but you would have to implement them differently for each RDBMS. In > addition, real life applications are much more advanced than simple > SELECT, > INSERT, UPDATE statements, and that's why i mentioned you would end up > with > different versions of queries for different RDBMS. I definitely agree with > William it's better to use abstraction in the code such as providers and i > mention about in my previous post. > > Best regards > -- > Milosz > > > "Gustaf" wrote: > >> Milosz Skalecki [MCAD] wrote: >> >> > Yes you can. OleDb is the old style way of abstracting database >> > providers. >> > The best way of doing abstraction is using stored procedures, as you >> > can >> > delegate sql queries to database, otherwise you end up with different >> > version >> > of queries for different RDBMSes. >> >> I agree that it would be neat to just call a stored procedure for the >> INSERT method I need. But a stored procedure I write for SQL Server can't >> be moved directly to Oracle, can it? I know nothing about stored >> procedures in Oracle. So I think I need to put the INSERT statment in the >> C# code, or possibly in a config file. >> >> > In addition, if you use .NET 2.0, it offers >> > another way od specialization for different RDBMS via providers and >> > factories: >> > http://www.simple-talk.com/dotnet/.net-framework/ado.net-2.0-factory-classes/ >> >> That's a good article. I was able to make use of the >> System.Data.SqlClient provider, but the OleDb provider did not work. When >> opening the connection, I get the useless error (type OleDbException): >> >> No error message available, result code: >> DB_E_ERRORSOCCURRED(0x80040E21). >> >> The app.config file currently looks like this: >> >> <?xml version="1.0" encoding="utf-8"?> >> <configuration> >> <appSettings> >> <add key="provider" value="System.Data.OleDb"/> >> <add key="connectionString" value="Provider=SQLOLEDB;Data >> Source=.;Initial >> Catalog=MyCompany;Integrated Security=true;User Instance=True"/> >> </appSettings> >> </configuration> >> >> The solution would still be very useful, if I can just change >> "System.Data.SqlClient" to "System.Data.OracleClient" at deployment. >> >> Gustaf >>
[quoted text, click to view]
William (Bill) Vaughn wrote: > No. Oracle uses different syntax, data flow and other methodologies in their > SPs. They are not compatible with SQL Server. I would write a data layer > that uses the OracleClient .NET data provider to access Oracle. So, to summarize, if I want to handle both SQL Server (which I need for development) and Oracle (for deployment), I shouldn't use stored procedures. Instead, I can write a DAL for SQL Server during development, and then use that as a template for an Oracle DAL? I'm not so familiar with the topic, so I hope someone can point me to an example on how to design a DAL. What I imagine is a class with a method that takes my business object as input, and return an error code in case something goes wrong with the connection or the SQL command.
There are whole books on the subject and no, it's not easy to do. While I
mention the approach in my books, I don't recommend it--especially for the inexperienced developer. Writing a data-centric application is more than just setting up queries and returning results. It also involves managing schemas, rights, uploads, downloads, procedures, backup, restore, exception handling and a lot more. The exception handling alone is a monumental task if you aren't developing against the actual database. While a data access layer can be done, it has to be written with a clear and complete understanding of both systems and how they interact with the low-level and high-level interfaces. If I were you, I would develop against the engine you expect to use during production. -- ____________________________________ William (Bill) Vaughn Author, Mentor, Consultant Microsoft MVP INETA Speaker www.betav.com/blog/billva 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. __________________________________ Visit www.hitchhikerguides.net to get more information on my latest book: Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition) and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ----------------------------------------------------------------------------------------------------------------------- [quoted text, click to view] "Gustaf" <gustafl@algonet.se> wrote in message news:OulluC7vHHA.5008@TK2MSFTNGP05.phx.gbl... > William (Bill) Vaughn wrote: > >> No. Oracle uses different syntax, data flow and other methodologies in >> their SPs. They are not compatible with SQL Server. I would write a data >> layer that uses the OracleClient .NET data provider to access Oracle. > > So, to summarize, if I want to handle both SQL Server (which I need for > development) and Oracle (for deployment), I shouldn't use stored > procedures. Instead, I can write a DAL for SQL Server during development, > and then use that as a template for an Oracle DAL? > > I'm not so familiar with the topic, so I hope someone can point me to an > example on how to design a DAL. What I imagine is a class with a method > that takes my business object as input, and return an error code in case > something goes wrong with the connection or the SQL command. > > Gustaf
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
| home · blog · groups | Questions? Comments? Contact the dn |