Database Design
Add to Cart
Database Design

It is a good idea to write down the purpose of the database on paper — its purpose, how you expect to use it, and who will use it. For a small database for a home based business, for example, you might write something simple like "The customer database keeps a list of customer information for the purpose of producing mailings and reports." If the database is more complex or is used by many people, as often occurs in a corporate setting, the purpose could easily be a paragraph or more and should include when and how each person will use the database. The idea is to have a well developed mission statement that can be referred to throughout the design process. Having such a statement helps you focus on your goals when you make decisions.

What is good database design?

Before creating database, first we must know the following things:
  • Duplicate information also called redundant data is bad, because it wastes space and increases the likelihood of errors and inconsistencies.
  • Accurate information is important. If your database contains incorrect information, any reports that pull information from the database will also contain incorrect information. As a result, any decisions you make that are based on those reports will then be misinformed.

Introduction
Add to Cart
Introduction

Subscribe to: Posts (Atom)