Sadly, No. A lot of existing organizations have business architectures that were 'designed' up by a VB programmer back when the company had a fraction of the transactional activity or amount or scope of data. Back then the quality of the design was unimportant, and it would have worked as well if the data was stored in flat files.

As the company grew to a point where they realized they needed a full time DBA (probably after being scared because of a database crash or getting hacked) the architecture becomes sort-of locked in. The powers that be usually adopt the attitude that "it served us well for the past 10 years.." so it will continue to do so, they just want a DB professional to make a few 'index tweaks' and do backups and improve security. The scalability and concurrency (or lack thereof) of the existing architecture is is never questioned because there is no conceptual understanding of relational database engines or the data designs that allow them to perform to their maximum potential.