Updating to Newest Stuff

[Randymarsh9]

I can see that a lot of new stuff has been added in since I made my server, so I am considering upgrading to the new db and rev. My server has a lot of custom stuff like npc stats, zone requirements, quests, pets, merchants. If I backed up all of those tables and then sourced them back, would there really be a point of going through the whole updating process? I'm inexperienced at upgrading a server and if I wouldn't benefit much from the changes, I don't want to risk screwing up my server.

[trevius]

This thread might help with some info about updating your DB:

http://www.eqemulator.net/forums/showthread.php?t=28245

But, if you just want to update to the latest SVN, all you should have to do is run the extra SQL that comes with it and make sure to get all of the required SQL added before starting your server up on the new code.

Also, it is a very good idea to backup your whole database before making any changes to it. Not worth risking a mistake.

[Randymarsh9]

Ok every thread I find seems to be saying to do something contradictory. If I just want to update my server to have the newest stuff thats been added since I created it, what should I really do?

[Randymarsh9]

Ok I'm trying to back up all of my custom stuff to an SQL file so then I can just source it back in, but everytime i send stuff to my updates.sql, it just erases what I put in there before it

[vales]

I'm going to use Rev621 seeing how it's the latest one for example's sake.

1.) Update your database to the latest revision you want. For example, if you're on Rev590 with your custom stuff, update all relevant SQL files up to Rev621.

That would mean you would need to source in:
600_group_leadership.sql
612_instance_changes.sql
615_adventure_assassination.sql
619_Adventure_Recruiter_Flavor.sql
621_LDoNTraps.sql


2.) Then export your custom stuff. This means your custom stuff is up-to-date with Rev621. Now you're all set.

3.) Source in your new database (not your custom stuff yet!). Make sure you keep an eye on the database you're using. For example, the latest PEQ database is peqdb_1129Rev610. This means the database has all updates up until Rev610.

This means you will have to source in any additional SQL files up until Rev621 which has the following SQL updates:
612_instance_changes.sql
615_adventure_assassination.sql
619_Adventure_Recruiter_Flavor.sql
621_LDoNTraps.sql


4.) Source in all of your custom stuff, and you should have no problems at all at this point. Since you made a backup with your custom stuff with Rev621 and you're sourcing in your custom stuff that's Rev621 ready, you should be all set.


The point is to make sure your custom stuff is matching with the revision you're sourcing in so there's no data/table conflicts.

[Randymarsh9]

ok well, I just see me trying something like that ending horrbily, so I'm never updating