Database Design Common Uses for One-to-One Database Relationships One-to-one relationships are the red-headed step-children of the relational database world. Here are 25 reasons it doesn't have to be that way.
Database Design Reader Question: How to Match Names from Multiple Systems It's a common data cleansing challenge: how do you eliminate duplicate data from multiple systems without accidentally deleting unique data?
Database Design When Should You Include an Autonumber Column in a Table? Surrogate vs. Natural Keys. GUIDs vs. Autonumbers. What factors dictate whether to include an autonumber column in your table? When should you do it?
Database Design Beware of "Over-Normalizing" Your Database Sometimes the two primary goals of database normalization--reduced data redundancy and improved data integrity--are at odds with each other.
Basic The Single Most Important Concept for Understanding Relational Databases If you're coming to the database world from the spreadsheet world, this one key concept will help you make the necessary mindset shift.
Database Design Sample Database Schemas for the Database Design Phase The most important phase of any Microsoft Access application project is the database design. This site has tons of sample schemas to get you started.
Database Design Reader Q&A: Single-Row Tables Are single-row tables something you should use or not? Can they be trusted? I answer that and more in this installment of Reader Q&A.
Database Design The 13 Kinds of Business Application Tables Database tables in a line-of-business application generally fall into one of these thirteen categories.
Database Design When to Store Numbers as Text Introducing the "Numeroliteral Test," a one-question heuristic for deciding whether to store numeric data in a character-based field.