DDD and relational database design

While reading Domain Driven Design (Eric Evans, Addison-Wesley) I've come to think of how DDD compares to relational database design (RDBD). I started working with RDBMS at the same I started programming and during my first two years in the industry I really dove in to RDBD.

The interesting thing is that I've always done RDBD based on the domains/clients point of view. And I imagine that it's quite normal when working with RDBD to ask yourself and the customer questions like "can a user have more than two accounts?", "do we really need to query for specific order rows, won't they always be returned (using outer join) when we query an order?" and so on to find out how what the customers perception of reality is, business rules etc. From my point of view this isn't at all much different from DDD. Designing the system/database as the domain/client/business sees it.

I may be way out of my league here but if this isn't totaly wrong then it at least helps me to learn and employ DDD faster, easier and more efficient.