Helpdesk Indexes and Constraints

Audience

Developers, database engineers, QA and support.

Summary

Indexes support tenant scope, canonical identity, activity chronology, SLA monitoring, assignment/comment/attachment history and outbox processing.

Reference Content

Unique indexes cover tenant/category name, tenant/priority name, tenant/ticket number, positive tenant/compatibility identity, tenant/SLA-policy name, processed event identity and outbox event identity.

Nonunique composites cover priority rank, ticket status/requester/assignee, child history by ticket/time, ticket SLA target and breach/due, escalation level, activity time and outbox status/time. Required text lengths are mapped for key business and integration fields.

No unique constraint prevents multiple TicketSla rows for the same ticket/target or multiple escalations for one SLA.

Requires confirmation

Index effectiveness, duplicate SLA/escalation protection, provider-specific filter portability and production index monitoring 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/20260709105542_AddHelpdeskCompatFields.cs

Related Articles

• Database overview
• Schema reference
• Database limitations

See Also

• API documentation
• Technical documentation

Keywords

Database index, unique constraint, filtered index, query performance.

Revision Information

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