In web.config file, to connect to Oracle database I use<BR><appSettings><BR> <add key="connectionString" value="Provider=MSDAORA.1;Data Source=XXX;User Id=YYY;Password=ZZZ" /><BR> </appSettings><BR><BR>I use MSDAORA.1 or OraOLEDB.Oracle.1 in provider section. Now our production server has Oracle 9.2 client installed on it and We have Oracle 8.1.7 in our dev environment. Do I need to change the provider in web.config file before moving to production?
If you are using System.Data.OracleClient, the connection string DOESN'T have a Provider attribute.<BR><BR>Are you telling me that you were previously using "Provider=MSDAORA.1;Data Source=XXX;User Id=YYY;Password=ZZZ" as the connection string for an OracleConnection? I did not think that would work. I think that you may have been using the System.Data.OleDb namespace with an OleDbConnection with that string. Right?
Actaully many of our ASP applications use oraoledb.oracle.<BR>Now our production server oracle client is Oracle 9.2 and we will be moving our first .net application to that server. Moving to .net, I am using oraoledb.oracle or MSDAORA.1 in the connection string and System.Data.OleDb namespace. It is working with Oracle 8.1.7 client. Sounds like that is not the right way.<BR><BR>So in web.config file, how should be the connection string?<BR>If using system.Data.OracleClient is better how should be the connection string in that case?<BR><BR>Note: MSDAORA.1 is not reliable though (with stored procedures).