Download Question

**cavedude** · #1 04-29-2009, 03:06 PM

The PEQ database on SVN is in one piece, really. At least all content data is in a single file. There are two other parts which are the player tables, which need to be separated so you do not lose toon data when you update, and the third is for the EQOffline system which is optional.

I just reorganized the SVN a bit and added a readme to hopefully make it less confusing. There was a time when it was a lot simpler, but with all the changes to player tables we have seen lately, and the fact that PEQ has a wide range of users which requires flexibility, simplicity needed to be exchanged for usability. Still, it's not overly complicated to install. Initial installs come down to sourcing 2 files, with a 3rd that is optional. Upgrades require dropping the content, sourcing it, and then applying any missing updates to player tables.

Aldest · #2 04-30-2009, 01:13 PM

Thank you CaveDude, that reorganization did, indeed, make it a whole lot clearer.

I'm still a bit fuzzy on updating my content to the new database. The tables that seem the same I just directly input. You mention that the character data has been modified a lot.

If I am taking my old DB and going to a new revision on a new server, is there any easy way to do this or is it simpler to have all my players recreate and just try to compensate them with levels/gear?

**cavedude** · #3 04-30-2009, 02:39 PM

The files in the updates folder will update all of your character tables without losing any toon data. You want to source in every update in that folder in order, from the last time you updated. If you have a db_version table in your database, that will tell you which version you are running. Just source in all updates after that point. If you do not have that table, then you'll need to compare the EQEmu changelog and what your database schema looks like with the updates files to see which you need to source. If it's really old, (before the EQEmu code moved to SVN) then you will need to source them all.

The actual content of the database is simple. Source drop_system.sql, and then source the file contained within the .gz file. Of course, this will destroy any custom content you have added to the server. The best way to keep that intact is to maintain a sql of all your changes, and source that back in after you've updated the content part of the DB.

Aldest · #4 04-30-2009, 03:25 PM

The custom content I have, thankfully, put into sql file. I'm confident I can get that back in. Simple inserts and the like.

To elaborate though, I am moving servers completely. From a workstation to a real server. So I'm sort of doing a "new server" and then a restore. I'm currently sourcing the full .gz file. I'll then source the load_player. I thought it would be easier to create a fresh start and then bring data over instead of upgrading my existing old revision.

My only confusion is how to get the character data in. I assume when you say you make constant changes to it that is in the column that is an actual file? When I back that up and source it in it appears to work. The characters are there and do seem to tie to the right tables but not completely. Gear is there but factions are messed up. I'm not sure if this is the same issue or an entirely different one. On my last attempt most of the monsters were indifferent and/or ally that should be KoS.

Can I directly go from my release (I want to say revision 222 honestly) to the newest or, at least just in the instance of characters, is it better to have my players recreate and then fix them? Or am I really just making this a whole lot more complex than it is (I tend to do that)?

Aldest · #5 04-30-2009, 08:59 PM

Okay, a bit of an update. I took my time today and followed all the instructions.

I was able to get my server working as intended and running. I haven't moved any of my custom content to it.

Basically my question is, before I do that, can I move characters directly from revision 222 to 440+. I did one as a test and it seems to work fine. If that is the case then I'm set and might write up a sort of "how to for those as slow as Aldest." If not, is there a way to "upgrade/convert" characters?

**cavedude** · #6 04-30-2009, 09:07 PM

In order to go from 222 to current, you'd need to apply all the updates from Rev227.sql to the current Rev438.sql. If you do that, your toons will all be fine and you won't have to worry about them anymore

Basically, if you can get your toon in-game, then you're set.

Aldest · #7 04-30-2009, 09:28 PM

Quote:

Originally Posted by cavedude

In order to go from 222 to current, you'd need to apply all the updates from Rev227.sql to the current Rev438.sql. If you do that, your toons will all be fine and you won't have to worry about them anymore

Basically, if you can get your toon in-game, then you're set.

That is great news =)

I really appreciate all the help on this. It looks like I've got everything set then. I'll play with it a bit more before making the official move but I think we're golden.