Outside of the physical limits of the host system (which should be easy to manage locally), the primary constraint is probably the capabilities of the backend database in use. On the latter your mileage may vary, and one should check with the authors and support team of your database of choice. However, I do think some thought should be given to an archive mechanism where closed tickets of a user defined age, and invalid customer, agent, and queue data can be stored after clean removal from the active otrs database. Not a trivial task I know, but if one has a very busy system one does not want things to get to slowed down by dead data, and as closed tickets records are retained this could become significant. On the other hand deleting records completely may loose important or useful data that may be useful to access at a later date. An archival mechanism would give the option of gracefully ageing data, and optimising performance. On Thu, 2004-12-09 at 11:13, Daniel Balan wrote:
Hello OTRS,
I have a question about how big OTRS can be. For example my OTRS has at this moment almost: 50 000 tickets and more than 150 000 articles. The articles are kept in the file system and the size exceed 20 Gb. I am using MySql on Linux (fedora core).
Does any one has a similar installation? Do you have any idea how big OTRS can be? Regards,
Daniel -- Meum est propositum In tabernum mori,
Graham Smith