• Information, information, information--it's everywhere all the time. In fact, it seems like there's too much information! How do we keep track of it all? That's what a database is for. Databases are collections of information stored on computers.
• Computers are great tools for storing information. They have huge memories and can recall information accurately. They are really helpful for dividing information into useful categories.
• Database developers and administrators tell the computer how to organize information. That is, they design and build databases.

What's a database?

• A database is just an organized collection of information.
• In fact, if you have a set of Pokemon cards and you've organized your cards by character, that's a kind of database. A database is a collection of information organized into categories--in this case, by character name.
• When you have a lot of information that you want to organize in more than one way it is very helpful to have a computer store it.
• You don't have to build your own database from scratch. You may have heard of Access or FileMakerPro. These are two ready-made database packages you can buy off-the-shelf.
• When people use databases, they access information by doing "queries." A user "queries" or instructs the computer to search its categories of information in order to find the answer to a specific question. The computer gives the user the answer in a "form" or "report." Queries, forms, reports... these are the vocabulary of the database administrator/developer and you will have to learn how to use all of them if you go into this field.

What's the work like?

• Database developers follow a product development cycle similar to that of programmer/software engineers. In general the development cycle of a database looks like this:
  
  1. Gather User Requirements: At the beginning of the cycle, a database developer interviews the people who will be using the database to find out what kinds of queries and reports the users need.
  2. Storyboard Design: The database developer will design the database. A web designer or graphics designer might work with the database developer to "storyboard" how the database will work. That is, draw a series of pictures showing how users will access the computer database and what kinds of answers they will get to a query. This storyboard will be shown to users for feedback.
  3. Build Database: The database developer will build the database and a data entry person will put all of the information into the database.
  4. Gather Feedback: Once the database is ready to use, the database developer will get feedback on how it works.
  5. Modify Database: Depending on that feedback, the database developer may make some modifications to the database.
  6. Maintain Database: Eventually, when the database is in a more finished phase, a database administrator takes over. This person is responsible for making sure that the database runs smoothly, is backed up regularly and is kept up to date.

What does it take to be a Database Developer or Administrator?

• Successful database developers are creative problem solvers.
• They like looking at problems and coming up with creative solutions.
• They like logic puzzles and thinking about how things fit together.
• They are team workers and understand how their work fits into the big picture of the organization.
• They are good communicators and can quickly understand what their customers want.
• Successful database developers typically have a strong background in math and computer science.

Interested in more? Look at entry level jobs in this field.