difference b/w

What is the difference b/w Database Architecture, Database Designer and
Database Developer
John wrote:
> What is the difference b/w Database Architecture, Database Designer
> and Database Developer
I'll start off the thread with the following rant:
The Database Architect is much like the Database Designer, but he has a
cooler sounding title. He (or she) has likely earned that title by
understanding not only the intricacies of relational database table
design, but also the harwdare environment. He can design a complete
system. Or maybe he can't. But he's going to cost you more than the
designer. The Architect probably has a B.S. in Engineering or Computer
Science. The Designer probably a B.A. in Music or Art History. They are
both equally likely to have initials after their name like MCSD and
MCDBA, but only the Architect could have a PhD. The Architect is a
well-adjusted person and prefers an office to a cube. Sometimes he gets
the office, sometimes not. He adjusts. The Designer always has a cube.
The Architect frequently speaks at conferences. The Designer frequently
speaks during movies. It's a small, but important difference.
The database developer is a software developer. He claims to know a
great deal about database design and query tuning, but is really just a
good .Net or Java developer with the know-how to create SELECT
statements and design a few stored procedures. He knows keys exist, but
he's not really sure what they're for or how to make them go away. Maybe
he does. I don't know. He commands a good salary if he can articulate a
point. Otherwise, he's happy with his secure job and his median salary.
He may have initials like MCAD. Up until the dot-bombs of a few years
ago, the developer frequently worked for an hourly wage as a consultant.
He still works hourly, but delivers your pizza instead.
David Gugick
Imceda Software
www.imceda.com