Wanted to share my experience here for future/current Sysaiders.
We started using Sysaid Pro version about 1 year ago, about 300 users, about 300 assets, at this point about 8K tickets. We don't use Knowledgebase too heavily or any other features - just straight Help Desk and Asset Management. Our DB size is getting close to about 1 GB and recently we've been having issues where internal backups are failing consistently then about a few days later, email to ticket conversion is getting very spotty - one email will convert, next will not. Not related to any particular user.
We sent it all to Sysaid support, and they say that they start seeing DB corruption for Derby at about 1 GB - this, in my opinion, is not a very large DB size to start seeing these kinds of issues. They have already repaired our DB, sent it back to us and now we are seeing the same issue two weeks later. They recommendation at this point is to migrate to a different DB, which we are planning to move to MySQL since that is also free (they say no limitations on MySQL concerning corruption issues).
It seems, to me, that if you're capable of doing so, starting off with MySQL might be a better approach. Granted, I have not even had to think of Derby once in the whole year (i.e. very easy to administer), but now that we depend on Sysaid so heavily to manage our Help Desk, it's tough when either its screwy with ticket conversion, or, when we have to disable it in order to repair and/or migrate the DB. Right now we're in the middle of another huge project and Sysaid has been crucial, so its a bad time to be forced to migrate.
Just putting this out there for others to reference.
If anyone has any tips/advice on MySQL for Sysaid (I know very little), that'd be appreciated.
This message was edited 1 time. Last update was at 01/06/2012 13:42:14
|
![[Post New]](/Sysforums/templates/default/images/icon_minipost_new.gif){kind=icon}
![[Up]](/Sysforums/templates/default/images/icon_up.gif){kind=icon}
