In most applications you're going to be doing both things, I remember Rail's ORM was always presented this way: it's the far better option for simple object relationships and CRUD style systems but you can still write raw SQL as needed for complex stuff or things requiring performance optimizations.

There's plenty of ways to manage complexity in software. Two or three different databases in a single app doesn't kill them, nor will two different DB interfaces.