Helpdesk Database Retention

Audience

Developers, database engineers, security, privacy, support and architects.

Summary

No Helpdesk retention policy, scheduled cleanup, archive process, partitioning policy or legal-hold implementation was found.

Reference Content

Ticket deletion is not exposed by the reviewed API. Attachment-reference deletion is explicit, but external file deletion is absent. Audit, timeline, processed-event and outbox rows have no expiry/cleanup implementation. Failed/processed outbox messages remain queryable unless another unreviewed operational process removes them.

Cascade deletion would remove three ticket child collections if a Ticket were deleted through the context; other identifier-linked rows have no configured cascade.

Requires confirmation

Retention schedules, archival, legal hold, audit/outbox cleanup, external document retention and data-subject deletion require confirmation.

Source References

• microservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.cs
• microservices/src/helpdesk-service/Infrastructure/Persistence.cs
• microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs

Related Articles

• Database overview
• Schema reference
• Database limitations

See Also

• API documentation
• Technical documentation

Keywords

Database retention, cleanup, archival, legal hold, outbox retention.

Revision Information

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