- Used Zammad version: Zammad Version 5.0.x
- Used Zammad installation type: Repository from Zammad
- Operating system: Linux Debian 10
- Browser + version: Opera LVL2 (core: 73.0.3856.400)
We are using one Zammad installation in our company to manage the support and to archive/hold on the complaint. For us it works very well and we have no problem.
My college from the quality management ask me: What is with the Tickets when we use Zammad more than 5 or 10 Years. Have we a miximum number of the Tickets, have we a maximum lifetime from the tickets? in example will the system delete older tickets than 5 or 10years? Have we a problem with the database when we reached a critical number of Tickets.
Thank a lot for your Help
Also interested in this. We seem to have performance issues. Wondering if 15,000 tickets could be causing an issue.
Is there a method to archive old tickets to PDFs or something “offline” (out of Zammad) to get performance back? We’d just drop those PDFs into Drive so they’d be indexed for continued searching.
15 thousand? Well that’s cute.
we have Zammad installations in hosted environment with more than 1,500,000 tickets and far more than 3,000,000 articles. No issue at all.
Zammad does not come with any restrictions as on per ticket, article and user number. It just doesn’t care and technically also doesn’t matter in terms of performance usually.
The technical limit is what comes with postgresql or mysql depending on your database server. You really don’t have to worry about that.
Most likely configuration (overviews hint hint), not followed system hardware requirements ( Hardware — Zammad documentation) or not yet done performance tunings (Configuration via Environment Variables — Zammad documentation). You may also want to check Configure Database server — Zammad documentation just to be sure you’re covered.
If that’s not helping pelase create your own thread.
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.