Database Administrator vs Database Architect? In terms of job responsibilities and activities, what is the difference between a Database Administrator (DBA) and a Database Architect?
I would say the term Database Administrator covers the full gamut of database duties: design, development, production support, performance tuning, report writing, OLAP, etc.

A Database Architect is involved in the design and development of large or complicated database solutions. However, the Architect is usually not involved in the day-to-day operations of the system once it is deployed.

I don't really like either term.  Database Administrator is too vague, Database Architect sounds pretentious.  

I am a computer programmer at heart, but aren't we all?