A carefully thought-out database design forms the foundation for future success. These links will help you plan your database designs to maintain performance and integrity through future growth.
What is a compound key? Find out in the About Databases glossary!
Looking for a description of default values and constraints in databases? The About Databases Glossary provides an easy to understand description.
Looking for a definition of a database relationship? Check out the About Databases glossary definition!
Looking for a definition of many-to-many database relationships? Read our definition in the About Databases glossary!
Looking for a definition of one-to-many database relationships? Read our definition in the About Databases glossary!
Looking for a definition of one-to-one database relationships? Read our definition in the About Databases glossary!
In our first article, we looked at the basic requirements of 3NF. Here they are again to refresh your memory: meet the requirements of 1NF and 2NF and remove columns that are not fully dependent upon the primary key.
In this article, we begin our look at the first of three major normal forms -- first normal form (otherwise known as 1NF).
As you may already know, databases use tables to organize information. Each table consists of a number of rows, each of which corresponds to a single database record. So, how do databases keep all of these records straight? It’s through the use of keys.
Databases are designed to offer an organized mechanism for storing, managing and retrieving information. They do so through the use of tables. If you’re familiar with spreadsheets like Microsoft Excel, you’re probably already accustomed to storing data in tabular form. It’s not much of a stretch to make the leap from spreadsheets to databases.
Looking for a definition of Object Oriented Databases? Find it here!
Looking for a definition of the database term stored procedure? Find it here in the About Databases glossary.
Databases depend upon keys to store, sort and compare records. If you’ve been around databases for a while, you’ve probably heard about many different types of keys – primary keys, candidate keys, and foreign keys. When you create a new database table, you’re asked to select one primary key that will uniquely identify records stored in that table.
Second Normal Form allows you to enhance the normalization of your database. In this article, we explore the requirements of 2NF and the process of normalizing your database.
All database management systems should share four characteristics: Atomicity, Consistency, Isolation and Durability.
Database normalization can save storage space and ensure the consistency of your data. Learn the basics in this introductory article.
What's best for your situation? Two-tier, three-tier or n-tier databases? Find out here!
Confused by the world of databases? Looking for a concise description of how databases work? Look no further! This article introduces you to the wonderful world of databases.
In the first installment of our database selection guide, we walk you through the process of defining the requirements for your database platform.
Is a DBMS like Microsoft Access, FoxPro, FileMaker Pro or Lotus Approach sufficient for your needs? Find out as we explore the world of desktop databases.
Does your organization require a server-based database like Oracle or Microsoft SQL Server? Join us as we explore the world of these high-performance systems.
Database normalization can save storage space and ensure the consistency of your data. Learn the basics in this introductory article.
Learn how to ensure that your database meets the fundamental requirements of first normal form (1NF).
Learn how to ensure that your database meets the data reduction requirements of second normal form (2NF).
There are a lot of desktop databases on the market. Which ones are the cream of the crop? Find out here!
This case study in automating billing procedures at the University of North Carolina provides a great overview of the database design process.
Louis Davidson brings us an informative look at the most common mistakes made by database designers.
The Massachusetts Institute of Technology offers lecture notes on database design including a case study from the City of Cambridge's Fire Department. (See lectures 4 and 5 through this link)
Follow this link for a comprehensive look at database normalization. A great resource for database designers of all levels.
Database normalization lecture slides from a design course at the University of California at Berkeley.
Simon Frasier University presents an illustrated introduction to entity-relationship (ER) diagrams.
This lengthy article covers the fundamentals of RDBMS design. Topics covered include normalization, integrity checking, keys and business rules.
Applied Information Science provides an in-depth tutorial on the various types of keys used in relational databases.
