Discussion Locked

Logical Database Design

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are currently moving from a mainframe to a network development environment. We are going to use SQLServer for certain types of application development. The question relates to how most organizations deal with Logical database design. With mainframe hierarchical databases the final word on logical design came from the database administration group. Relational database design, and in particular SQLServer database design is not as involved a process. In fact physical database design in SQLServer is not rocket science either. The question is, do most departments still rely on database administrators as the experts in both logical and physical database design in a SQLServer environment, or does the developing Analyst do the logical andsometimes the physical design? If database administration is still intimately involved in this process are organizations using processing requirements for communication between the database administration personnel and the systems analysts? If processing requirements are completed are they different than what was completed in a mainframe environment?

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 jim.schromm

A DBA or Database programmer should design the database because poor database design will impact the performance of applications using the data. Also, be careful not to skimp on the initial design for small applications that are transferred to SQlServer. The next thing you know someone will ask to expand the application (scope creep kills) and you will be redesigning the entire database or trying to sell your existing database as "not too slow."

by james.schlitter

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.

This discussion is closed to new replies.