(mm)o(rpg) database design – multiplayer and network programming – gamedev. net

I think what you should do is figure out what I, as a user of your system, would actually want, before you figure out what the system looks like. Database entity I think starting to design “a system” in a vacuum of requirements is putting the cart before the horse.

Am I a third party developer? If so, how do I connect to your system? How do you make sure that my users can’t edit data that they shouldn’t be able to edit?

Or am “I” really just yourself, as a game developer? If so, what information do you need to store about your customers? About your customers interaction with the game? About the game itself?

For example, it’s often useful to separate “customer” from “avatar” — I may want to have multiple avatars for a particular customer.

Database developer However, modern games (such as Wizard 101) realize that there are possibly many “customers” for one “payer” — a family may play a game, but only Mom pays the credit card.

Additionally, you may have multiple server instances — do “avatars” (characters) travel between instances, or are they stuck to a particular instance?

How does payment work? Is it free to play? Do I pay per zone? Pay per month? Pay once and get to play forever? Do you think you will provide all three options at some point? If not, how do you know the option you pick is the right one? How do you know why a particular “payment expires” field has the value it has? What if someone calls in and complains that their expiry is wrong?

Where do customers come from? Banner ads? Word of mouth? Radio advertising? Magazine inserts? Store check-outs? Do you need to know, for each customer, to do a better job of selling your game? Do you need to know which customers stick together so you can market their relation — or mine the relation to find scammers, fraudsters and griefers?

If I have characters, can they be shared with other users on the same payer account? At the same time or separate times? Do users get tagged with specific attributes, like “over 18” or “over 13” or whatever? Or does that live with “characters”? Do you want to keep logging information about how a characters is used, by which user, at which time, so you can later go back and look it up?

I have no idea of knowing whether these are use cases that matter to you or not, so I have no idea whether your table schema will serve a purpose or not. Data recovery plan I think it would be much better if you asked a question something like:

“here are my use cases, and here is the schema that realizes these use cases, and I think that N database server instances will serve M users with an assumed query rate of Q per hour — is that about right?”

even goverment with a SUN FIRE 15K with 80 64-Bit Ultra sparc processors and a Hitachi cabin for data Storage…. Data recovery kansas city sad but true…Governments aren’t accountable nor do they give a choice. N k database If they choose to, they can “delete” voters and nobody can do much about it.

If running a for profit company, lose 5 minutes of data of some vocal user and your credibility is destroyed, permanently plastered over google search results.

Before anybody blames me, want to make a backup every our? every minute? it is ok!you wont loss date at all but performance will drop when doing itIt’s just an engineering problem. Data recovery 2016 If you want streaming backups or straight up replication, it can be done. 510 k database fda No problem really.

that’s why companyes make backups at night when nobody is working on the computers..The reason large companies and governments use Oracle or DB/2 is leverage. Database programmer If something goes wrong and they lose a day’s worth of accounting information, causing their yearly IRS report to be missing $3 million, they just point at the big company who is then responsible for fixing it. Data recovery osx Or they will sue them or something.