Database Review Checklist

Project Name

Objects Reviewed

Reviewer Name

Review Date

DBD Version

Reviewer Column
ID Items to be considered (Y/N/NA)
Have you defined Primary key (Auto increment Identity fields)
and Foreign keys
Have your defined indexes for Columns used
a) in Joins
b) in Search conditions
c) Foreign key fields
d) Order by Clause
Have you stored Large Object columns (like Image, Text etc.) in a
different table than the main table, and put a reference to the
large object in the main table.
Have you chosen appropriate data type with optimal size e.g.
decimal for storing monetary values, unsigned int instead of int
(unless you are storing negative values) etc.
Ensure collation is utf8_unicode_ci unless there is some specific
need to select other collation set
Have you maintained following columns in your tables
created (datetime)
modified (timestamp)
status (tinyint)
Please check there are no comma separated values being stored
for referenced IDs.
Table relationships are following the rules of data integrity and
related columns have same data type.
Text data type is not used unnecessarily.
Unicode support is provided in the data type if data needs to be
stored in multiple languages or possibility of storing it in future.
Date columns are not storing it in varchar format.
Stored procedures are not using Dynamic Text SQL statements
unless really required.
View is created if application needs frequent information in the
form of related data.
Allow null values constraint is supported for optional data values.
Gives performance boost.
Advanced features if implemented
Implemented constraints for data validation and integrity.
Implemented triggers for data validation.
User defined functions for complex backend code.
User defined data types to store compound objects.
Full text search support.