Helpdesk Database Relationships

Audience

Developers, database engineers, QA and architects.

Summary

Exactly three explicit relational relationships are configured, all from Ticket to owned child rows.

Reference Content

CategoryId, PriorityId, SlaPolicy category/priority identifiers, TicketSla ticket/policy identifiers, escalation ticket/SLA identifiers and attachment CommentId are stored as scalar values without configured foreign keys.

This allows application-level joins but does not provide database referential enforcement or cascading behavior for those fields.

Requires confirmation

Whether missing foreign keys are intentional, deletion semantics, orphan detection and aggregate ownership require confirmation.

Source References

• microservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.cs
• microservices/src/helpdesk-service/Infrastructure/Migrations/20260708165325_InitialHelpdeskSchema.cs
• microservices/src/helpdesk-service/Infrastructure/Migrations/HelpdeskDbContextModelSnapshot.cs

Related Articles

• Database overview
• Schema reference
• Database limitations

See Also

• API documentation
• Technical documentation

Keywords

Foreign key, relationship, cascade delete, scalar reference.

Revision Information

• Status: Draft
• Last reviewed: 2026-07-20
• Next review: 2026-10-20