Creature Handler Archive
Thread: Survey: Do you really use all your pets in your datapad?
Message Edited by Freth on 09-13-2004 08:42 AM
HoundMB wrote:
The difference is that the pets take up database space on the servers. You can see from recent steps including the e-mail system changes, merchant changes, mob spawns, etc. that they are scrambling to find space to hold everything.
digiwrath wrote:
HoundMB wrote:
The difference is that the pets take up database space on the servers. You can see from recent steps including the e-mail system changes, merchant changes, mob spawns, etc. that they are scrambling to find space to hold everything.
it's not that they don't have space. they have plenty of money to afford that.
the problem is that their database is, quite frankly, a piece of crap. and it has problems managing all the data that's in it, so they're slimming it down and hoping things improve.
Message Edited by SioBabble on 09-13-2004 07:34 AM
digiwrath wrote:
HoundMB wrote:
The difference is that the pets take up database space on the servers. You can see from recent steps including the e-mail system changes, merchant changes, mob spawns, etc. that they are scrambling to find space to hold everything.
it's not that they don't have space. they have plenty of money to afford that.
the problem is that their database is, quite frankly, a piece of crap. and it has problems managing all the data that's in it, so they're slimming it down and hoping things improve.
I'm afraid as a database consultant I have to (reluctantly) agree here
.
If database size is a serious issue, I'm afraid there is something very wrong with the underlying database design.
With correctly designed indexing and procedures, data storage and retrieval should not be an issue. Oracle can handle databases into the Tera-byte range - a pet represents only a few tens of bytes at most (unless the designer has done something stupid). Sure there are a lot of them, but not so many that it should cause an issue.
The only area where an understandable bottleneck is likely to occur is with "transient data" where records are being rapidly created, deleted or moved about - and pet and item storage does not fall into that category.
But then again, designing good databases is a pig (which is why I get paid the big bucks!
)