An Introduction to Database Design: From Logical to Physical

This is one of the more popular posts on this blog, so I am re-blogging it today… enjoy!!!

Data and Technology Today

A proper database design cannot be thrown together quickly by novices. What is required is a practiced and formal approach to gathering data requirements and modeling data. This modeling effort requires a formal approach to the discovery and identification of entities and data elements. Data normalization is a big part of data modeling and database design. A normalized data model reduces data redundancy and inconsistencies by ensuring that the data elements are designed appropriately.

From Logical…

So, database design is the process of transforming a logical data model into an actual physical database. Technicians sometimes leap to the physical implementation before producing the model of that implementation. This is unwise. A logical data model is required before you can even begin to design a physical database. And the logical data model grows out of a conceptual data model. And any type of data model begins with the discipline of data…

View original post 1,811 more words

About craig@craigsmullins.com

I'm a data management strategist, researcher, and consultant with over three decades of experience in all facets of database systems development and implementation.
This entry was posted in DBA. Bookmark the permalink.

4 Responses to An Introduction to Database Design: From Logical to Physical

  1. Pingback: DB2 Hub | An Introduction to Database Design: From Logical to Physical

  2. Vonani says:

    1. What specific tasks can a DBA do during:

    A. Conceptual database design phase
    B. Logical database design phase
    C. Physical database design phase

  3. Read my book on Database Administration for more in-depth coverage of this topic.

  4. naresh kakadiya says:

    Best

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.