Page 1428 - (ISC)² CISSP Certified Information Systems Security Professional Official Study Guide
P. 1428

bringing a database table into compliance with normal forms is

                  known as normalization.
                  Although a number of normal forms exist, the three most common

                  are first normal form (1NF), second normal form (2NF), and third
                  normal form (3NF). Each of these forms adds requirements to
                  reduce redundancy in the tables, eliminating misplaced data and
                  performing a number of other housekeeping tasks. The normal
                  forms are cumulative; in other words, to be in 2NF, a table must

                  first be 1NF compliant. Before making a table 3NF compliant, it
                  must first be in 2NF.

                  The details of normalizing a database table are beyond the scope of
                  the CISSP exam, but several web resources can help you
                  understand the requirements of the normal forms in greater detail.
                  For example, refer to the article “Database Normalization
                  Explained in Simple English”:

                  https://www.essentialsql.com/get-ready-to-learn-sql-database-

                  normalization-explained-in-simple-english/



               SQL provides the complete functionality necessary for administrators,
               developers, and end users to interact with the database. In fact, the
               graphical database interfaces popular today merely wrap some extra
               bells and whistles around a standard SQL interface to the DBMS. SQL
               itself is divided into two distinct components: the Data Definition
               Language (DDL), which allows for the creation and modification of the
               database’s structure (known as the schema), and the Data
               Manipulation Language (DML), which allows users to interact with the

               data contained within that schema.


               Database Transactions

               Relational databases support the explicit and implicit use of
               transactions to ensure data integrity. Each transaction is a discrete set
               of SQL instructions that will either succeed or fail as a group. It’s not

               possible for one part of a transaction to succeed while another part
               fails. Consider the example of a transfer between two accounts at a
               bank. You might use the following SQL code to first add $250 to
   1423   1424   1425   1426   1427   1428   1429   1430   1431   1432   1433