September 21, 2000 10:21 PM

Responsible Denormalization

Rating: (0)
SQL Server Magazine
InstantDoc ID #9785
How to break the rules and get away with it
In the first column I wrote for SQL Server Magazine (SQL by Design, "Why You Need Database Normalization," March 1999), I set out some rules to live by for database design. Recently, I wrote a six-part series about data modeling in which I revisited the topic of data normalization. While developing the sample SQLmag database in these articles, I showed how to normalize data. (See the sidebar "The SQLmag Database DDL Script File," page 75, for information about how to get a copy of the Data Definition Language—DDL—file that created this database.)

When y...

...This article is for paid Professional Members only.

Already a Professional Member? Please log in now:

NOT A PROFESSIONAL MEMBER? YOU CHOOSE:

Professional Membership

Monthly

Annual

VIP Membership

Monthly

Annual

Add a Comment

Hallow!!

I've got some questions I want you to please help me answering them, they are about physical database design.

Denormalization

The problem is that the denormalisation may create duplicated data.

1.What is the data that may be duplicated?
2. Why this can be a problem? On other words, what kind of anomalies can be produced in the database when there are duplicated data? How can this affect DATA INTEGRITY?

Davids Shingenge 5/3/2004 5:21:22 AM


Excellent Article, it outlined everything and clarified everything I needed to know.

sue4/13/2004 6:56:59 AM


I have several questions, among them,

1. Can a candidate key be referenced by another table?
2. Do you really mean that denormalization means merging table?

Phil Wang 5/11/2001 1:07:18 PM


You must log on before posting a comment.

Are you a new visitor? Register Here
GOOGLE LINKS
SPONSORED LINKS
FEATURED LINKS