Designing a database is one of the most crucial parts of the database creation process and if done improperly, may result in serious repercussions. It is very important that the programmer considers what information he or she intends to hold in the database. In order to do this, the programmer must set up tables and attributes such that relationships can be formed between tables in order to facilitate the exchange of information.
The database programmer is responsible for creating an organized and relevant tool. He or she must display relevant and only relevant information as not to distract the user with useless clutter. Attributes in a table should be related somehow to the table itself and to each other. In other words, it is crucial for the designer to give the users the information they need and not to give them information they don’t. User-friendliness is key!
Keeping attributes on track will also allow the programmer to link tables, which allows both users to retrieve and combine information from different tables. If the programmer designs the database in this way, he or she can use relationships between tables to create alternate views of the information held in the database.
Database design is similar to the design of any instrument; it lays out the building blocks for the item to be built. If the building blocks are not laid properly, the user will encounter problems. Some problems may be insignificant such as a bit of irrelevant information, but some problems that have more to do with functionality have the potential to create more large-scale destruction. As long as the programmer thoroughly considers the database design and tests for errors, a database has the potential to be an invaluable tool.
