I'm curious what folks are using to abstract the underlying DBMS from your .NET apps. I know lots of shops that just pick a RDBMS and run with it - and have simpler designs - that would be nice. But lets say you need to support both ORACLE and SQL Server?
You can program to the ADO.NET interfaces so instead of SqlConnection or OleDdConnection use IDbConnection or use OleDdConnection always and sacrifice performance. But what about the actual SQL statements? How do you virtualize the variants? String tables in resource only assemblies? Do you put everything in stored procs and simplify the SQL embedded in your code? Or Don't use stored procs because you have SQL statement generation code a la RogueWave's DBTools. I'd love to hear all strategies big and small. Thanks Jim You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
