"Oracle", "Sybase", "SQL Server" vs just "SQL/JDBC" in the CV
- by bobah
How would you define a testable measure of the expertise that, if you're honest with yourself, lets you write in your CV words "Oracle", "Sybase", or "SQL Server" and not just "Relational Databases, SQL, JDBC" in your software developer's CV? What every XXX-developer (XXX - a vendor name) should know?
The question is similar to http://stackoverflow.com/questions/2119859/questions-every-good-database-sql-developer-should-be-able-to-answer but is vendor-specific.
Below is a start of the list as an example, demonstrate what kind of answers I am hoping to get.
If you are expert in X then you know that Y (X - Y below):
Sybase/SQL Server - they are very similar, Sybase is much more expensive
Sybase/SQL Server - for Java you can use either native Sybase/JSQLDB driver or jTDS that is using TDS protocol and can connect to SQL Server as well, TDS traffic can be dumped and analyzed with hexdump command
Sybase/SQL Server - for C++ you can use FreeTDS to connect to any, for Perl - same
Sybase/SQL Server - a query can return multiple result sets and return codes, all need to be processes otherwise errors can happen
Sybase/SQL Server - sp_help, sp_helptext
Sybase/SQL Server - your tables/views/procedures are under DBName/dbo/...
Sybase - for C++ on Linux you can use Sybase client API to connect (at least until recently)
SQL Server - JDBC driver has a configurable transparent failover capability
Oracle - for C++ Linux one can use OTLv4 that is a very powerful yet lightweight wrapper around Oracle client API
Oracle compilation (contributors: ammoQ)
PLSQL
Java Stored Procedures
'' is null
Hierarchical Query
Analytic Functions
Oracle Text
