Imagine yourself being responsible for creating the curriculum for a degree program called Databases.

What subjects? What lectures? How would you structure the optimal curriculum?

Only one condition: it has got to be vendor-neutral.

What value am I proposing to provide to my students? Staying "vendor neutral" means you're never actually touching a database, so I'm not sure who this degree is for.

- Inadequate lecture title: PL/SQL or T-SQL.

+ Adequate lecture title: Procedural programming for database development.

-----

Another adequate suggestion would be Databases and the Relational Model, altough Edgar Codd published his famous paper during his time at IBM research.

What flavor of degree? Is this a college program, a practical program, an employer sponsored program? That will make considerable difference in what areas get what level of focus. It will also make a lot of difference in naming, since they all use different nomenclature and sometimes use the same word with significantly different meaning.

-PatP

Let's say the imaginary college offers a bachelor and a consecutive master course.

great database guys and girls are not trained. they are born that way.