Page 1 of 1

Sticky SQL Mess (potentially)...

Posted: Tue May 05, 2009 12:50 pm
by MPH2008
I have just completed testing of Hesk2 on our test server and made all the appropriate GUI modifications and other tweaks necessary for it to work.

However, the problem is that we have an existing Hesk running on our live server which the manager wants all the 10,000 tickets merging across to be compatible with the uptodate version.

I have attempted importing the databases across but it won't let the old one overwrite on the new test server, likewise the new database onto the old. Importing to a dropped database will result in the script breaking.

I'm aware there was an upgrade option during installation, however this is on the live server and about 2 weeks of modifications and refinements have been made to the latest HESK to my companies' standards/specifications.

Is there a way to copy the old live database across to the new test server HESK to test that it works OK, and then to copy the entire lot across to live server to minimise downtime and remove any potential for loss of tickets?

Many thanks in advance!

Posted: Tue May 05, 2009 4:17 pm
by Klemen
Well the only advice I can give is:

1. backup database and files on the Live server
2. upgrade the Live server to 2.0 on low-traffic hours (at night or early morning)
3. if it's not working properly you can still delete the 2.0 files and database and install the backup.

Posted: Wed May 06, 2009 1:20 pm
by MPH2008
So once upgraded I should be able to copy the modified css and php files and then run the DB php patches to get it working again?

Sound's like a plan - cheers Klemen for your time :D

Posted: Wed May 06, 2009 2:29 pm
by Klemen
That's the idea. Backup -> upgrade (-> modify) -> test (-> delete and restore backup if needed).

I don't know what kind of changes you made or if there were any changes to the old install so I can't give any guarantees, but that's how it would normally work.

Posted: Thu May 07, 2009 10:26 am
by MPH2008
Indeed - I did make some changes to the original, however I don't think I changed the databases in anyway, so it should be OK to run the upgrade this way. :)

Posted: Fri May 08, 2009 9:10 am
by MPH2008
That ran a treat on the development server, so i've scheduled in this afternoon for the official upgrade. A few files didn't overwrite automatically however I can copy them manually from the dev-server.


:wink: