When we need to use 1-to-1 relationship in database design?

by

  1. Vertical partitioning for large tables to reduce I/O and cache requirements — separate columns that are queried often vs rarely.

  2. Adding a column to a production system when the alter table is “too expensive”.

  3. Super-type/subtype pattern.

  4. Vertical partitioning to benefit from table (join) elimination — providing optimizer
    supports it (again to reduce I/O and cache) .

  5. Anchor modeling — similar to 4, but down to 6NF.

More Related Contents:

  1. How are super- and subtype relationships in ER diagrams represented as tables?
  2. Is storing a delimited list in a database column really that bad?
  3. Should each and every table have a primary key?
  4. What’s the difference between identifying and non-identifying relationships?
  5. Database, Table and Column Naming Conventions? [closed]
  6. Can I have multiple primary keys in a single table?
  7. What are database normal forms and can you give examples? [closed]
  8. Normalization: What does “repeating groups” mean?
  9. Difference between scaling horizontally and vertically for databases [closed]
  10. Relational table naming convention [closed]
  11. Best practices for storing postal addresses in a database (RDBMS)?
  12. When I should use one to one relationship?
  13. Why use a 1-to-1 relationship in database design?
  14. What is the optimal length for an email address in a database?
  15. What are the advantages of using a single database for EACH client?
  16. Database optimization orders
  17. In what way does denormalization improve database performance?
  18. Best representation of an ordered list in a database?
  19. Alternatives to Entity-Attribute-Value (EAV)?
  20. have address columns in each table or an address table that is referenced by the other tables?
  21. Minimum no of tables that exists after decomposing relation R into 1NF?
  22. Limit an sqlite Table’s Maximum Number of Rows
  23. NULL permitted in Primary Key – why and in which DBMS?
  24. What are some best practices and “rules of thumb” for creating database indexes?
  25. What’s the better database design: more tables or more columns?
  26. Should OLAP databases be denormalized for read performance? [closed]
  27. Best beginner resources for understanding the EAV database model? [closed]
  28. Derived account balance vs stored account balance for a simple bank account?
  29. In a StackOverflow clone, what relationship should a Comments table have to Questions and Answers?
  30. uncertainty in developing a database model

Leave a Comment