There seems to be something that you miss in this discussion: Writing applications!
It's very likely very true, that you can use your DBA skills from one database
and apply them on another, but many application developers have truely failed
to understand that the different databases are very different in how you
treat them well. Even the most simple applications that do nothing but 'select
* from tab where primary_key=<something>' can be coded efficiently
against one database, where the same code will neither perform nor scale
if executed against the other database.
The converse is fortunately also true: With a well chosen design and well
chosen application coding principles, you can write applications that both
run, perform and scale on multiple different databases and at the same time
are relatively portable between them. At the very least, the well chosen
design will allow you to clearly distinguish portable from non-portable code.
/Bjørn.
- Re[4]: Know 1 database, know them all? Robert Eskridge
- RE: Know 1 database, know them all? Orr, Steve
- RE: Know 1 database, know them all? Broodbakker, Mario
- RE: Know 1 database, know them all? Stephen Lee
- Re: Know 1 database, know them all? Mogens N�rgaard
- Re: Know 1 database, know them all? Anjo Kolk
- Re: Know 1 database, know them all? Mogens N�rgaard
- RE: Know 1 database, know them all? Post, Ethan
- RE: Know 1 database, know them all? Broodbakker, Mario
- Re: Know 1 database, know them all? Mogens N�rgaard
- Bj�rn Engsig
