7 replies
by wayne m.
For most applications in the business world, yes, we rely on database administrators for database design.
There is a great deal of thought and effor that goes into relational database design. There are the issues of partitioning the design into tables and determining the relationships. What data needs to be split into multiple tables and which should be managed as a single table? What keys are needed? What tables have direct relationships and which have indirect? When should, if ever, data or information be duplicated in multiple tables? When should indices be used?
For small database design, a DBA is probably not needed. For larger databases, however, the value of a knowedgable DBA in the design is immense.
by rlyons
by jim.schromm
by rlyons
You need DBA's skilled in relational database design and data normalization practices. This is somewhat more complex and convoluted than mainframe codacil, since performance can be intimately tied to the design of table relationships. There are some very good products, like ErWin and PowerDesigner, which can be used to assist in this process.
We allow application programmer/analysts to do initial table layout and data definition, but the DBA still has to integrate their design and needs intothe overall corporate data model (physical and conceptual) and then perform the actual CREATE activities (NEVER let a p/a do this step). A DBA is always assigned as part of a project team to assist in data design and management issues.
DBA work isnot complete when the tables are built and populated. They are also responsible for monitoring and dealing with rogue processes, tuning for performance, and sizing issues for tablespaces and temp spaces.
by rlyons
by rlyons
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending