B
Just about everything Oracle has been involved in is a joke, except for their database.
The database is top-notch... SQL Server proponents like to think they're trading a little bit of performance for a lot of usability, but the reality is that the GUI used to administer SQL Server sucks.
Take the backup/restore dialog, for example. Until recently, it exhibited only garden variety stupidity. It was, like, the one Microsoft dialog that apparently had no concept of filename extensions, and was just generally clunky. In the most recent versions, though, Microsoft has redesigned the dialog to be far, far worse.
My favorite part: restoring a backup file defaults to putting the restored file over the location from which it was backed up, even if you change the name of the database you're restoring to. Imagine a scenario where you have a copy of the data that you restore/trash/restore repeatedly during development... better remember to change that target data file name every fucking time, or you'll trash the database (production?) from which the image backup was originally taken.
Oh, and the fancy GUI that's used to maintain your schema? A lot of the time it pussies out, forces the table edit window closed, and saves the fucking name of the object you were trying to edit (and nothing else) to a text file. What the fuck does that accomplish? And I'm talking about ordinary changes where the corresponding ALTER TABLE command goes right through, e.g. making a column NOT NULL in an empty table.