When queried, most database professionals would mention normalized as one of the most important characteristics that tell the difference between a good and bad relational database design (whether they know what the term "normalized" means or not.) Normalization is a key to great relational designs, but there is so much more to be considered. A normalized database that suffers from poor naming, too many or too few indexes, terrible interfaces, and so on can derail your design's value to the user. In this session I will present primary characteristics of a design that differentiates between an ugly design that will have your colleagues nitpicking you to death and one that will have them singing your praises. Characteristics such as comprehendible, documented, secure, well performing, and more (including normalized, naturally) will be discussed.
Louis Davidson has worked in the IT industry for over 25 years as a corporate database developer and architect. He has been a Microsoft SQL Server MVP for 15 years and has written five books on database design, and contributed to many other SQL Server books as an author and tech editor. He has a bachelor's degree in Computer Science from the University of Tennessee at Chattanooga. You can read more about Louis at http://drsql.org.