|
|
Posted by Gordon Burditt on 11/13/07 00:37
>Ever had to split a website + SQL Tables ?
Splitting a web site does not, by itself, require using more than
one MySQL server.
>Have a UNIX pc-linux-gnu on i686 + FEDORA
>
>1) We have to split a sub-domain for the main domain name.
This does not require more than one web server. You can host
thousands of domains on a single web server. (A single domain,
e.g. google.com, can have lots more traffic than a thousand low-traffic
domains).
>2) We have to build a transfer and merge from Tables hosted on Server
>1 TO Tables hosted on Server 2.
Splitting a web server does not require using more than one MySQL server.
If you are attempting to do cross-joins between the databases for two
different domains, it would work better to put them on the same MySQL
server.
Why do you *HAVE* to split the database server?
>1) We do not know if www.bobby.com can be host on SERVER 2 and
>xoaks.bobby.com can be host on SERVER 1.
Yes, you can have separate web servers on separate machines for
separate domains. A MySQL server doesn't know anything about domains,
so you don't HAVE to split it, but you might want to. Or not.
>We do not manage subdomains. We are affraid to not to be in a position
>to get xoaks.bobby.com working normally on SERVER 1.
>
>2) Some data will be stored in Tables on SERVER 1 from
>xoaks.bobby.com.
>
>These MYSQL data stored in tables on SERVER.1 must be integrated in
>the SERVER.2 database.
The web servers on BOTH machines could use the MySQL server on
either machine (or an entirely separate one).
>SOLUTION 1 : A non-appreciated solution is an event from the contab
>that download tables in SERVER1, send tables onto SERVER2, and SERVER2
>merge the tables into its operating Database. SERVER2 aknowledge
>SERVER1 to delete fine-integrated data.
>
>[Flying Tables] So risky sheme !
>
>OTHER Solution : How SERVER MYSQL Berkeley DB 3.2.9a on SERVER.1 could
>directly communicate to the MYSQL database hosted on SERVER.2.
Navigation:
[Reply to this message]
|