Database Verification Checklist

1. 
   

   Verify that each table contains the required number of fields for recording information. This is an important step because users will not be able to enter information if there is not field for that information.

   
   


2. 
   

   Verify the existence of Forms and their relationship to the database. If there are existing forms they should relate to their target records.

   
   


3. 
   

   Make sure that correct triggers are in place. For instance, If no repetition is allow, a trigger should fire a message box indicating that no duplicate is allow. Triggers can also be use for other possible types of errors due to null values, or wrong character type. They can also be use for other events, such as the execution of additional programs.

   
   


4. 
   

   Check that each column is properly and uniquely identified. This is an important to prevent duplicate data from entering the database.

   
   


5. 
   

   Verify that data type and values are set for each field. The purpose of this step is to prevent user errors due to typing of characters in numeric fields and vise versa. Similarly, data entry should not exceed the maximum and the minimum number of character per cell.

   
   


6. 
   

   Make sure that proper data sorting has been set for each field. It is always good to organize data in a orderly fashion, either in an ascending or a descending order, it makes the records more accessible.

   
   


7. 
   

   Verify that each column accepts the correct data type. This is important because if the purpose of a field is to collect numeric values for calculations, then text should not be allowed to be recorded in the field, the same applies for numeric values in text fields.

   
   


8. 
   

   Verify the setting of minimum and maximum cardinality at each entity. If more than one student are to be taking classes at a particular is school the minimum cardinality should be >1 and the maximum can be that of (M) Many.

   
   


9. 
   

   Check restriction for “Null” or “Not Null”. This is important to make sure that users do not leave empty cells.

   
   


10. 
    

    Test any existing query to make sure that they return desired results. Each query should include only specific data. So, eliminating any unnecessary record from the query will facilitate the understanding of the results.

    
    


11. 
    

    Query the database for redundant data. Redundant data affects database performance, so it is good to delete any duplicate record.

    
    


12. 
    

    Delete any existing duplicate. This will improve database performance.

    
    


13. 
    

    Verify that referential integrity has been set and that records update accordingly. Verify that child tables are not accepting input that has already been recorded on other tables. This is important because it prevents duplicates. Similarly, updates that are made to one table should reflect on other relations.

    
    


14. 
    

    Check that there is a correct relationship between tables by making sure that they are using an adequate type of relationship (1:1, 1:N, N:1, N:M). This is important because one customer can order many parts, and many parts can be ordered by one customer; however no part can order a customer.

    
    


15. 
    

    Re-check Normalization. Re-check the previous steps to make sure that the database complies with proper normalization.