Unfortunately, all the db's mentioned have "enhancements" to the SQL specification that can very quickly make your SQL code db specific. There are 2 things to consider:
1) Is this for a specific Project? Are you planning on building an particular application?
2) Is this about the Database, and DBA routines, and Serverside SQL programming, or about getting data out of the DB.
If it for a specific project, you need to consider the specs and eventual architecture.
If it's about managing or programming a database, each db has SIGNIFICANT differences. Pick one or more and become proficient.
If it's about gettting data in/out of a db, choose an access method (odbc/jdbc/.Net/oledb/DBI/etc.) to interface with, and choose any one you feel comfortable with, even MS Access. The more generic the access method, the less the backend DB matters.
Jay Grubb
Technical Consultant
OpenLink Software
Web:
http://www.openlinksw.com:
Product Weblogs:
Virtuoso:
http://www.openlinksw.com/weblogs/virtuoso
UDA:
http://www.openlinksw.com/weblogs/uda
Universal Data Access & Virtual Database Technology Providers