• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 407
  • Last Modified:

Table with Too many Relationships

I am developing a sql database for an help desk application.  I am a little concern because my Ticket table have about 16 other relationships and I was wondering if the design is correct or should I break up the table?  See the attach file for the diagram.Database Schema
  • 2
1 Solution
Scott PletcherSenior DBACommented:
In general, w/o regard to this specific design, 16 in and of itself is not too large a number of table relationships.

In fact, if you fully normalize, you end up with way more tables than you'd have thought possible, even for a fairly routine-size design.
One observation that I have is in regards to 2 FKs in the Ticket. There are 2 tables, ProductOrServiceType and ProductOrServiceCategory, first as a child refers the second as parent. In this case I don't think the ticket table should have FKs to both these 2 table as it is the case in the diagram. It should only have a FK to ProductOrServiceType, which in turn refers to ProductOrServiceCategory.

Probably there are other similar situations hence the number of FKs in Ticket table is more than it needs to be.
vnewman29Author Commented:
Zberteoc thanks for your comments.  I am removing some of those unnecessary FKs.
Well, if my comments were useful and you actually intend to follow them means that I would have been entitled to some points. :o)

No problem but next time this happens make sure you split the points.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now