ServiceDesk Database Sizing
Updated: 13 Feb 2012 | 1 comment
This issue has been solved. See solution.
What could one roughly expect for the size of the Ensemble or ProcessManager database on a typical, though mildly customized (with about 20 custom workflows) install of ServiceDesk Solution that services about 3,000 employees? I know this could vary wildly but just want a ball-park average to start on.
Discussion Filed Under:
Comments
A few GB
I would expect this to weigh in at a few GB, maybe up to around 5GB early on. This is highly variable, especially with custom workflows.The table I would worry about most is Messages, which can get large. That aside, the best thing to do for your SQL database is to make sure the recommended best practices are in place. We highly recommend these:
1. Recovery Model is Simple.
2. Nightly maintenance consisting of Rebuild Indexes, followed by Update Statistics.
Those elements in place should keep the SQL database manageable and performing well. If your db is growing too fast, you may want to review your custom projects, also.
Would you like to reply?
Login or Register to post your comment.