What is the difference between data administrator and database designer?

Answer 1

(Additional answers or links to help answer the question are welcome.)

Answer

Well, assuming that you are not a IT person, my answer is that the administrator is someone that manages the information(data) and databases(the boxes) and the designer creates the database schema (the way the data should be stored in the database, logic and physic). In my opinion, this two concepts should be always together, I mean, the DBA must know administration and design of databases.

Answer

The database administrator (DBA) should know something of database design, and in a small shop the DBA might handle both the administration and the data design. But since both areas (database administration and database design) require a lot of different and extensive knowledge and experience, best results can be had when there are experts in both areas. The DBA will work closely with the system administrator and may in fact also be an SA. The database designer will work closely with the software developers, as the data structure is integral to the software application. Of course, the database administrator and the database designer must coordinate with each other throughout the project.

The DBA works with the RDBMS (relational database management system) itself and should know how to install and configure the RDBMS application. The DBA will work with the SA on tuning the system to best support the database engine and the database usage. The DBA and SA will work on sizing, storage, and backup management. The DBA is ultimately responsible for backups and everything else to do with data integrity (at the database level). The DBA will monitor data handling operations and either make database-level changes to improve performance or, through analysis, capture information to pass back to the data designer or development staff for their use in improving their usage of the database.

The database designer should understand something of software development and applications structure. The designer will learn from the applications designers the data types, quantities, relationships, and desired operations (searches, sorts, updates, etc.) and work with the developers to design a structure/schema that will meet the requirements of the software application in terms of function and performance and at the same time assure data integrity. The designer will be considering matters such as unique keys, primary and foreign keys, data types, counters, naming, table relationships, search and sort elements, database normalization, search and sort efficiency, and data integrity.