I'm just installing a new server running Windows Server 2008 R2 Standard and SQL Server 2008 Standard. Both are 64-bit editions. Before I complete my installation is there anything wrong with this configuration for running SysAid? Is there anything in particular I should do? And how do I go about migrating from a Derby database on a standard PC where it has been running for over a year to my new SQL Server?
I can't help you in regards to migration from Derby to SQL ... but
I can let you know that I've done a clean install of version 6.5 and 7.0 on a Windows 2008 machine with SQL 2005 and 2008 and I did not have any problems. Just make sure TCP/IP is enabled for SQL and you have the right permissions setup. As I said I'm of no help in regards to Derby to SQL migration but I know what you want to move to works
We are running Sysaid 7.0.04 in a Windows 2008 R2 64bit virtual machine with a SQL 2008 backend residing on the same machine and it is working great. In regard to the migration - We had our migration done a week or so ago by the superb sysaid support team. Sysaid support requested the necessary information from us and migrated the database from derby to ms sql 2008 over the weekend. They did an excellent job and it went off without a hitch.
Thanks for the info, it's good to know that my set up will work, in theory at least! I'll get in touch with SySaid Support when the time comes, I'm very impressed that they'll do the migration for me! I don't think I know another software product for which the support is so good.
I have a problem. I have SysAid with MySql 2008. But the action builder in the escalation rule don't work.
I was forced to migrate the database from MySql 2008 to Derby. Now all works but I want to use the MySql database.
Have you got any news about this issue?