Database design for a survey [closed]

by

I think that your model #2 is fine, however you can take a look at the more complex model which stores questions and pre-made answers (offered answers) and allows them to be re-used in different surveys.

– One survey can have many questions; one question can be (re)used in many surveys.

– One (pre-made) answer can be offered for many questions. One question can have many answers offered. A question can have different answers offered in different surveys. An answer can be offered to different questions in different surveys. There is a default “Other” answer, if a person chooses other, her answer is recorded into Answer.OtherText.

– One person can participate in many surveys, one person can answer specific question in a survey only once.

survey_model_02

More Related Contents:

  1. How to implement a many-to-many relationship in PostgreSQL?
  2. How to implement one-to-one, one-to-many and many-to-many relationships while designing tables?
  3. Create unique constraint with null columns
  4. Subqueries vs joins
  5. What are best practices for multi-language database design? [closed]
  6. Database Structure for Tree Data Structure [closed]
  7. Are soft deletes a good idea? [duplicate]
  8. Database Design for Revisions?
  9. Database Design for Tagging [closed]
  10. Storing money in a decimal column – what precision and scale? [closed]
  11. How to store a list in a column of a database table
  12. Serial numbers per group of rows for compound key
  13. PostgreSQL: Which Datatype should be used for Currency?
  14. Why (and how) to split column using master..spt_values?
  15. Is there common street addresses database design for all addresses of the world? [closed]
  16. Facebook database design?
  17. How to create a multi-tenant database with shared table structures?
  18. Name database design notation you prefer and why?
  19. Can I set ignore_dup_key on for a primary key?
  20. Select (retrieve) all records from multiple schemas using Postgres
  21. Which datatype should be used for currency?
  22. Use email address as primary key?
  23. Composite Primary Keys : Good or Bad?
  24. SQL ON DELETE CASCADE, Which Way Does the Deletion Occur?
  25. Which database design gives better performance?
  26. What is the best way to implement soft deletion?
  27. Is there a severe performance hit for using Foreign Keys in SQL Server?
  28. How important are lookup tables?
  29. Historical / auditable database
  30. Designing SQL database to represent OO class hierarchy

Leave a Comment