The problem with this approach is that you can't use any of the databases at their best. For example, stored procs many times give you a performance advantage over dynamic SQL, but they can't be used because the code is different on each database. Views may or may not be supported on the target database. My advice is to drop the idea and just support one.

>Hi
>
>I wish to design my .NET app to be portable to multiple databases such as MYSQL, Oracle, MSSQL
>
>May I know which of the following strategies is best in terms of flexibility and ease of delivering maintenance updates to clients:
>
>1. Use Store Procedures
>2. Use Views
>3. Use SQL stored in some user defined tables with following fields
> a. DB_Type
> b. SQL_ID
> c. SQL Command
>
>Your advice much appreciated.
>
>Best Regards