Articles on all things data...

10 questions to ask before you build a database

 October 6

by Andrew Richards

How to build a database

…or at least how to start the process.

Microsoft Access does amazing things.

We can use it to store, analyse, report on, and manage data. We can get it to automate our business processes, to download CSV data from an FTP site and upload it again as a PDF. To allow users to input data and to email them to let them know when they need to do so.

But where does all this begin? How do you start that process? In a nutshell…

How do you build a Microsoft Access database?

If you’ve never used Microsoft Access before, there’s good news – the first phase doesn’t actually need you to use Access. Or indeed any other software – pencil and paper will work just fine. You see…

Planning is everything

The more work you can do in planning the database, in being clear what you want the database to do, and not do, the less likely you are to need to spend time re-designing and re-working the database when you’re half way through.

So, kick off by getting a good, clear understanding of the scope of the database. Talk to all the people who are going to be using it. Talk to those who will put the data in, and to those who will want to get it out, report on it, analyse it and so on. Find out what they need the database to do.

10 questions to ask before starting to build an Access datbase

  • What business process will the database support?
  • How do they currently manage that process?
  • How are those processes likely to change as the business grows or changes over the next 5 years?
  • What existing systems - paper-based or computer-based - will the database be replacing?
  • How many people need to use this new system?
  • Of those people, how many are likely to want to use it concurrently?
  • How much data will the database store? For example, are you wanting to store sales transactions that could run to tens of thousands per day? Or manage a manufacturing process, involving a few hundred items a week?
  • To what extent is security important? Is it simply enough that the data is stored reliably? Or must different people have access to different parts of the data?
  • Will this new database system have to connect to other systems? To your accounts package? To Outlook to send automated emails or schedule appointments? To an FTP server to import data?
  • Forgetting time, and budget, if your new database system could do anything for you and your business, what would you have it do?

So, in short, get a really good picture of what's needed. And think big! That's why the last question in the list is important - it's surprising how often people say "I don't suppose it's even remotely possible, but what would be really great is..." and they come up with something that's actually pretty simple! Of course, the converse is the number of times people will say "We just need a minor tweak so that..." and it turns out to be a major headache! But either way, it's a significantly easier thing to make design changes at this stage, on paper, than it is to make the changes when the database is built.

share this

Related Posts

Sign up now to be the first to hear about new articles!