What we would like to achieve?
Well an application that is capable to:
- change at runtime the database is it using, kind of change connection string and run on the “another” database
- creates all database objects needed regardless of the database, theoretically speaking all have tables, columns, indexes and so forth.
- read the catalog information, in plain English to be able to read the database structure
I do hope that at the end of this series or articles you will be capable to write an application doing just that, I know for sure that is possible 
.
Issues to solve:
- Different styles of connections strings
- SQL syntax and database capabilities related to SQL language support
- General programming issues
- Data types
- DDL
- CRUD
- Obtaining the schema
- Using Views
- Representing in the application the database
- Programming pitfalls to watch out
- Exception categorization
- Data provider behavior differences
- Database design issues
- Data types used
- Views
- Stored procedures and functions