| Lesson 5 || Data normalization |
| Objective || Define data normalization. |
Define Data Normalization
When you design the tables in your database, you also define the relationships between them. This process defines how the data will be stored in the tables. When you normalize a database, you organize the data in tables in such a way that the data does not repeat.
Typically, you end up with a greater number of tables, each containing fewer columns and a greater number of defined relationships.
Generally, it is a good idea to normalize, because it will result in tables having more clustered indexes. Tables with clustered indexes usually require less disk
space than tables that are not normalized, and they enable the software to execute queries more quickly. This is not always true, however, because normalizing increases the number of tables, and the more tables you use in a query, the more slowly the query is likely to execute.
The basic concept of normalization is to remove repeating columns (as much as possible) and place them in one or more new tables.
View the SlideShow below for an example of normalization.
Data Normalization Stages
The following table assesses the potential impact of normalization on performance, maintainability, extensibility, scalability, availability, and security.
This table is directly related to one of the Microsoft 70-029 exam objectives.
||Normalizing your database can tend to hurt performance if data tables are very large and your queries need to join many tables together.
||Normalized tables are much easier to maintain than non-normalized tables, because normalized tables have less columns.
||Extensibility generally refers the ability to upgrade your applications in the future. Microsoft determines whether specific functions and features are available to support your existing database designs. Therefore, normalizing your database will not have any impact on its extensibility.
||Scalability allows you to migrate your database onto other operating systems, such as Windows 89 or 2012. Scalability is affected when you incorporate database features that aren't supported by other operating systems. However, scalability is not impacted by normalization.
||Availability is a term that is used to describe SQL Server being on-line and available to process data. A highly normalized database that contains much data might affect the availability of the server while very intensive queries are being processed. Therefore, if you normalize your database, your server may not be available for other tasks if you have lots of data and lots of normalized tables.
However, many different query techniques can be employed to minimize this, such as using Stored Procedures.
||Security restrictions can be placed on tables or columns. However, it is easier and more convenient to place security restrictions on entire tables. Therefore, if you normalize your database, you can enhance security by restricting access to a table that represents a complete object, or entity, such as salary information.
Now that you have learned about data normalization, you will learn about data denormalization in the next lesson.
Data Normalization - Exercise
Before moving on to the next lesson, click the Exercise link below to get some hands-on practice with data normalization.Data Normalization - Exercise