![]() ![]() Now that you have learned about data normalization, you will learn about data denormalization in the next lesson. 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. These anomalies include data redundancy, spurious relations in the data, and loss of data. In all the stages, the data is selected by keeping in mind that there should not be any anomaly in the data grouping. However, it is easier and more convenient to place security restrictions on entire tables. The 3 stages of normalization of data in the database are First Normal Form (1NF), Second Normal Form (2NF), and Third Normal Form (3NF). Database normalization is a technique of organizing the data in the database. Relational databases are the most popular databases used by enterprise applications to store persistent data to this day. Security restrictions can be placed on tables or columns. However, many different query techniques can be employed to minimize this, such as using Stored Procedures. 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. A highly normalized database that contains much data might affect the availability of the server while very intensive queries are being processed. Database normalization is a database schema design technique, by which an existing schema is modified to minimize redundancy and dependency of data. However, scalability is not impacted by normalization.Īvailability is a term that is used to describe SQL Server being on-line and available to process data. Scalability is affected when you incorporate database features that aren't supported by other operating systems. Scalability allows you to migrate your database onto other operating systems, such as Windows 89 or 2012. ![]() Therefore, normalizing your database will not have any impact on its extensibility. Microsoft determines whether specific functions and features are available to support your existing database designs. Normalized tables are much easier to maintain than non-normalized tables, because normalized tables have less columns.Įxtensibility generally refers the ability to upgrade your applications in the future. Normalizing your database can tend to hurt performance if data tables are very large and your queries need to join many tables together. This table is directly related to one of the Microsoft 70-029 exam objectives. ![]() The following table assesses the potential impact of normalization on performance, maintainability, extensibility, scalability, availability, and security. ![]()
0 Comments
Leave a Reply. |