Tags: 3rd, application, attempt, cworks, database, databases, design, erd, form, mysql, normalisation, normalise, normally, oracle, sql, tend, uni

ERD and Normalisation

On Database » Database & Application

916 words with 1 Comments; publish: Thu, 06 Dec 2007 05:42:00 GMT; (25062.50, « »)

When i design databases for uni cworks i tend to design my ERD and then attempt to normalise but the design is normally always in 3rd normal form. Is this because the problems are trivial and not that difficult or is it that i'm making mistakes with my method of designing.

My understanding is that normalisation is a technique for spotting mistakes in the design stages?

This is always a problem when trying to produce documentation to support c works in that the normalisation section is always of limited contents.

All Comments

Leave a comment...

    • Don't worry - this just means that you are naturally good at database design! Normalisation is really just formalised common sense, so a good database designer tends to get it right first time without any formal normalisation stage.

      If that causes a problem with your class work, then I guess you'll just have to purposely denormalise your ERD a bit first!

      #1; Tue, 11 Dec 2007 21:23:00 GMT