View Full Version : More than 1 domain and MySql using 1 package
Christiaan
03-13-2007, 01:32 AM
More than 1 domain and MySql using 1 package.
Can each domain use MySql ?
I can read but it does not quite sink in what it means.
Can anyone just give a very, very simple explanation?
I did have a look at the various articles etc. but it seems that if one wants two or more sites on the one package, MySql is only for the main one.
Quick answer is no.
Will both domains be pointing to the exact same content, or different content?
If the same content (IRO) yes, but why (would be considered duplicate content by search engines; better to redirect to one domain now)
If different content, (IRM) no, IRM's (domains presenting different content) are not allowed mysql access.
sheila
03-13-2007, 01:40 AM
Only full hosting packages can have access to MySQL. And their IROs, DS-IROs and DS-IRMs. (IRMs cannot have access to MySQL.)
Full hosting packages are listed here:
http://www.FutureQuest.net/Services/Packages/
or, in summary table format, here:
http://www.FutureQuest.net/Services/Compare/
All of the above packages can access MySQL.
You also have the ability to put extra domains on your hosting package (overlay domains). There are essentially two types of overlays. IROs and IRMs. IROs are domains that point to the exact same website. IRMs are domains that appear to point to a different website.
The IROs can have MySQL access (appear to be the same website).
The IRMs cannot have MySQL access (appear to be a different website).
Also, subdomains that use the full hosting package's domain
blog.mydomain.com
(this would include DS-IROs and DS-IRMs)
These can have MySQL access.
Full explanation of different overlay domains (IROs, IRMs, etc) here:
http://www.FutureQuest.net/Services/IR/
The basic idea, is that if the URL appears to point to the main domain, then it can have MySQL access. If it appears to point to a different domain (not the main domain) then it cannot have MySQL access, and instead would need to be set up on a full hosting package of its own for MySQL access.
On one hand (not too long ago in another thread) I was bemoaning the loss of value of IRM's now that everything under the sun requires mysql access and IRMs aren't allowed to access mysql. On the other hand, the new power of the entry-level packages here are a real bargain now, and by splitting projects between individual packages you gain the advantage of distributing your content over many different servers.
vBulletin® v3.6.8, Copyright ©2000-2009, Jelsoft Enterprises Ltd.