Skip to main content
  • 1353 Accesses

Abstract

By now, you should have the conceptual and logical model created that covers the data requirements for your database system. As we have discussed over the previous four chapters, our design so far needn’t follow any strict format or method. It didn’t have to be implementable, but it did have to cover the requirements that are data related. In some cases, the initial creator of the logical model may not even be a database professional, but a client who starts the model. Changes to the logical model meant changes to the requirements of the system.

Nobody realizes that some people expend tremendous energy merely to be normal. —Albert Camus

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 44.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2012 Louis Davidson with Jessica M. Moss

About this chapter

Cite this chapter

Davidson, L., Moss, J.M. (2012). Normalization. In: Pro SQL Server 2012 Relational Database Design and Implementation. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-3696-2_5

Download citation

Publish with us

Policies and ethics