When it comes to planning our database, we need to consider a few different factors.
The first of these is how many tables we will need, a table being a part of our database that contains only one kind of information – a table containing customer details will only ever contain customer details for example, as a table containing orders will only contain information relating to those orders.
What these tables will be called should be considered to be unambiguous as to their purpose.
Within these tables, we will have multiple “fields”, columns in our table that contain one piece of information relating to our table. A customer details table is likely to contain their name, which would be broken down into forename and surname, for example, and may contain their address similarly broken down.
Similarly, we may like to consider which of these fields may be required and how they will be filled out to maintain data integrity, as we can flag these fields as required and choose how they need to be filled out to be valid. Maintaining integrity is important, as without it we may encounter problems, inconsistencies, or inaccuracies within our data which will cause issues down the road.
Who has access to our database may also be an integrity concern, as data protection is important – failure to maintain access integrity may lead to legal penalties.