> [EMAIL PROTECTED] wrote: > > > > Also this is just one option: The solution doesn't have to involve > MySQL at all; I just want the cheapest, most perfect solution (of > course ;). > > In order to help you with that, we need a more elaborate list of > criteria. For instance, against which events should the solution > guard that 'just a database' doesn't do? What is the relative > frequency and importance of those events? >
Thanks for the reply, Jochem. One reason that "just a database" won't do is a simple matter of being honest to our proposal. That is, somebody here told 'em we'd do it, and now we've gotta do it. The reason it went into the proposal is: 1: Clustered databases sound "cool" and "sexy" (Yes, that's a real reason :) 2: Unplanned failures (Very Rare): It would be nice if the motherboard fried on one machine, and we could fairly quickly (ideally, seamlessly) get the other up and running. 3: Planned outages (i.e., maintenance -- Rare): It would also be nice to take a machine out of the cluster to, say, add memory. We have no reason, at this point, to give any priority whatsoever to load balancing, BTW. Does this help? I'd be happy to elaborate further! Thanks very much, Jamie ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:202911 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
