This report will provide analysis on the relational database prototype for Rubind Incorporated and will explain three different benefits such as splitting the data into a number of different tables and storing specific information only once, enhanced functionality when carrying out complex queries and the ability to add future records. The report will also examine the costs and risks of using a relational database, the importance of data modelling by system designers, training methods and objectives, the importance of utilising back-up and recovery procedures and provides recommendations for future considerations. This report ultimately recommends creating a management team that reviews the future business requirements and whether changes are needed. There would also be an advantage to keep an up to date Data Dictionary that describes all the tables in the relational database prototype so future changes can be tracked.