Database Systems Audit
Your organisation already uses databases, but you want to be sure it is performing correctly and efficiently. Why would it not?
Even if your database began life as a well-designed application with no idiosyncrasies or inconsistencies, over time, this state of perfection can degrade. Some of the reasons for this degradation are:
All of these problems, and many others, can be corrected by a professional audit of the database design and of the data itself.
As a first step, the entire database schema is documented. The schema is the description of the data elements of the database, including the field types and sizes, their attributes, constraints, default values, index properties, relationships, link types etc. as well as view (or query) design.
The schema is an essential tool for identifying potential problems related to the data design (as opposed to form and report design), and is useful as a starting point for making modifications and extensions.
Troubleshooting and data correction
Using the schema, problems in the design can be identified and a plan constructed for correcting the problems. In order to correct a design without losing information, it may be necessary to create new queries and functions. Faulty data can also sometimes be corrected, but this may need to be accomplished in collaboration with the data users.
After changes have been made, a new schema document will be created.
A database audit is recommended on a regular basis in order to keep a database in tip-top condition and performing to expectations. On request, a review of the user interfaces (navigation, form design, report design, etc) as well as application functions, backup policies, security issues etc can also be undertaken.