Surrogate vs. natural/business keys [closed]

by

Just a few reasons for using surrogate keys:

  1. Stability: Changing a key because of a business or natural need will negatively affect related tables. Surrogate keys rarely, if ever, need to be changed because there is no meaning tied to the value.

  2. Convention: Allows you to have a standardized Primary Key column naming convention rather than having to think about how to join tables with various names for their PKs.

  3. Speed: Depending on the PK value and type, a surrogate key of an integer may be smaller, faster to index and search.

More Related Contents:

  1. Can I have multiple primary keys in a single table?
  2. What are the design criteria for primary keys?
  3. Is storing a delimited list in a database column really that bad?
  4. What’s the Hi/Lo algorithm?
  5. Should each and every table have a primary key?
  6. Database, Table and Column Naming Conventions? [closed]
  7. How are super- and subtype relationships in ER diagrams represented as tables?
  8. What are database normal forms and can you give examples? [closed]
  9. Difference between scaling horizontally and vertically for databases [closed]
  10. NoSql vs Relational database
  11. Best practices for storing postal addresses in a database (RDBMS)?
  12. Is it fine to have foreign key as primary key?
  13. What is the most efficient way to store tags in a database?
  14. Why use a 1-to-1 relationship in database design?
  15. What is the optimal length for an email address in a database?
  16. What are the advantages of using a single database for EACH client?
  17. GUID vs INT IDENTITY [duplicate]
  18. Database optimization orders
  19. In what way does denormalization improve database performance?
  20. Still Confused About Identifying vs. Non-Identifying Relationships
  21. Alternatives to Entity-Attribute-Value (EAV)?
  22. have address columns in each table or an address table that is referenced by the other tables?
  23. Minimum no of tables that exists after decomposing relation R into 1NF?
  24. Is it better to use multiple databases with one schema each, or one database with multiple schemas? [closed]
  25. Limit an sqlite Table’s Maximum Number of Rows
  26. When we need to use 1-to-1 relationship in database design?
  27. Need help in developing DB logic
  28. Should a database table always have primary keys?
  29. Databse architecture (single db vs client specific db) for Building Enterprise Web (RIA) application on cloud
  30. Database – Data Versioning [closed]

Leave a Comment