MESSAGE
| DATE | 2014-11-26 |
| FROM | Ruben Safir
|
| SUBJECT | Subject: [NYLXS - HANGOUT] [mrbrklyn@panix.com: [LIU Comp Sci] Why Normalization Failed to
|
From owner-hangout-outgoing-at-mrbrklyn.com Wed Nov 26 13:57:32 2014
Return-Path:
X-Original-To: archive-at-mrbrklyn.com
Delivered-To: archive-at-mrbrklyn.com
Received: by mrbrklyn.com (Postfix)
id 0316816112F; Wed, 26 Nov 2014 13:57:32 -0500 (EST)
Delivered-To: hangout-outgoing-at-mrbrklyn.com
Received: by mrbrklyn.com (Postfix, from userid 28)
id E0679161143; Wed, 26 Nov 2014 13:57:31 -0500 (EST)
Delivered-To: hangout-at-nylxs.com
Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89])
by mrbrklyn.com (Postfix) with ESMTP id 0C43616112F
for ; Wed, 26 Nov 2014 13:57:30 -0500 (EST)
Received: from panix2.panix.com (panix2.panix.com [166.84.1.2])
by mailbackend.panix.com (Postfix) with ESMTP id CD95B139C8
for ; Wed, 26 Nov 2014 13:57:29 -0500 (EST)
Received: by panix2.panix.com (Postfix, from userid 20529)
id AB58C33C87; Wed, 26 Nov 2014 13:57:29 -0500 (EST)
Date: Wed, 26 Nov 2014 13:57:29 -0500
From: Ruben Safir
To: hangout-at-nylxs.com
Subject: [NYLXS - HANGOUT] [mrbrklyn-at-panix.com: [LIU Comp Sci] Why Normalization Failed to
Become the Ultimate Guide for Database Designers?]
Message-ID: <20141126185729.GA29757-at-panix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: owner-hangout-at-mrbrklyn.com
Precedence: bulk
Reply-To: hangout-at-mrbrklyn.com
----- Forwarded message from Ruben Safir -----
Date: Wed, 26 Nov 2014 02:18:49 -0500
From: Ruben Safir
To: ping-Tsai Chung , Samir Iabbassen
, learn-at-nylxs.com, ping-Tsai Chung
Subject: [LIU Comp Sci] Why Normalization Failed to Become the Ultimate Guide
for Database Designers?
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101
Thunderbird/31.1.0
http://papers.ssrn.com/sol3/papers.cfm?abstract_id=905060
Why Normalization Failed to Become the Ultimate Guide for Database
Designers?
Marin Fotache
Al.I.Cuza University of Iasi
May 1, 2006
*Abstract: *
With an impressive theoretical foundation, normalization was supposed to
bring rigor and relevance into such a slippery domain as database design
is. Almost every database textbook treats normalization in a certain
extent, usually suggesting that the topic is so clear and consolidated
that it does not deserve deeper discussions. But the reality is
completely different. After more than three decades, normalization not
only has lost much of its interest in the research papers, but also is
still looking for practitioners to apply it effectively. Despite the
vast amount of database literature, comprehensive books illustrating the
application of normalization to effective real-world applications are
still waited. This paper reflects the point of view of an Information
Systems academic who incidentally has been for almost twenty years a
practitioner in developing database applications. It outlines the main
weaknesses of normalization and offers some explanations about the
failure of a generous framework in becoming the so much needed universal
guide for database designers. Practitioners might be interested in
finding out (or confirming) some of the normalization misformulations,
misinterpretations, inconsistencies and fallacies. Theorists could find
useful the presentation of some issues where the normalization theory
was proved to be inadequate, not relevant, or source of confusion.
*Number of Pages in PDF File:* 41
*Keywords:* database design, normalization, functional dependencies,
multi-valued dependencies, normal forms
*JEL Classification:* L86, M1
working papers series
----- End forwarded message -----
|
|
