On Tue, 19 Mar 2002, Young Sul wrote:
> Hi,
>
> I've got a website that uses a mysql backend database. Due to the way in
> which
> the database and development has been architected, I'm unable to
> load-balance
> the database between multiple DB servers, taking advantage of replication
> inhere
Young Sul wrote:
>
> Hi,
>
> I've got a website that uses a mysql backend database. Due to the way in
> which
> the database and development has been architected, I'm unable to
> load-balance
> the database between multiple DB servers, taking advantage of replication
> inherent
> in mysql. (this
At 22:13 2002-03-19, Young Sul wrote:
>Hi,
>
>I've got a website that uses a mysql backend database. Due to the way in
>which
>the database and development has been architected, I'm unable to
>load-balance
>the database between multiple DB servers, taking advantage of replication
>inherent
>in mys
On Tue, Mar 19, 2002 at 10:13:09PM -0500, Young Sul wrote:
> Currently, I mirror the master DB on another server, and can switch over
> ...manually...
> if the master dies.
>
> I'm wondering if others on this list have encountered a similar situation --
> how did
> you finally architect your DB e
Hi,
I've got a website that uses a mysql backend database. Due to the way in
which
the database and development has been architected, I'm unable to
load-balance
the database between multiple DB servers, taking advantage of replication
inherent
in mysql. (this is due largely to developmental const
