Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a problem with a database design:

I have an EReport. This EReport will have a QAPCategory. User must select a QAPCategory from an set of QAPCategory.

To know which QAPCategory can be selected I have done this design:

enter image description here

Is this correct? Is this a circular reference?

share|improve this question
So an QAPCategory belonga to one EReport and an EReport has also a relation to one special QAPCategory? – ypercubeᵀᴹ May 19 '12 at 7:27
What does the FK1 | QAPCategory.eReportID represent? – Jeroen May 19 '12 at 7:58
There is a list of QAPCategory that can be chosen from an EReport (QAPCategory.eReportID), and an EReport must have a QAPCategory (EReport.qapCategoryId). – VansFannel May 19 '12 at 8:13
up vote 2 down vote accepted

There's no need for both relationships.

Generally speaking, your category table should have one row per category, not per fact table row.

It's OK if multiple EReport rows refer to the same category record, but having a category record per EReport record defeats the purpose of normalizing in the first place.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.