Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Let's get the non-options out of the way right away. You don't want to do #3 and #4 is a non-solution. Magento Enterprise Edition doesn't add any features that will let you run multiple customers from one store.</p> <p>Now, onto possible options. As you state, #1 will allow you to update one version of the code, but of course this comes with some risks. As I understand it, your customers will need to access the stores? If you have multiple customers running on one database and one codebase, you will always run into issues with them affecting each other. For instance, who will control product attributes, which are by nature global? If one store deletes a product attribute, other stores may lose data as a result. If you solve this issue, what about catalog promotions and product categories, etc. Magento was built to handle multiple websites, but not to insulate them from each other, and you <em>will</em> experience problems because of this. As for performance, a large product catalog or customer base will tend to slow down the site, but you can mitigate this using the flat product catalog and making good use of caching.</p> <p>For option #2, you can run multiple Magento stores, which brings up two main problems. First, as you state, is updating the sites. If you are using a vanilla installation of Magento and not modifying core files, this should be a nonissue. Magento's updater is pretty simple for those installations, with difficulty increasing as you do more mods and have to use more manual processes for upating.</p> <p>As far as performance, running multiple magento sites <em>might</em> be slower, but it depends on how you structure them. Regardless of having one or multiple sites, you'll have to load data for each site, so database size won't be terribly different. File size on a server is pretty much a nonissue. In either case, when a customer requests a page, Magento has to spin up the entire framework to serve the request, which is where performance issues start to show themselves. One of the big mitigations for this is to use an opcode cache like Xcache, but with multiple machines you need to give Xcache much more memory to hold all the installations' code. Legitimate problem.</p> <p>My recommendation? Start on one machine, multiple installs. Work your way up on number of installs, and when the server doesn't support any more, move on. Keep your code changes out of the core and use extensions that can be easily updated, so updates are easy. That should mitigate as many of the concerns as possible.</p> <p>Hope that helps!</p> <p>Thanks, Joe</p>
    singulars
    1. This table or related slice is empty.
    1. PORunning Magento for multiple clients - single Installaton vs. multiple installations
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJoseph Mastey
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORunning Magento for multiple clients - single Installaton vs. multiple installations
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI suppose it does not really matter weather enterprise has the feature or not from a choice point of view as I am not going to be getting it. But I was assuming that if the enterprise edition could run multiple client websites then the AITOC module might be the way to go as its just adding support for what's already been done in a more advanced version. If Magento cannot ever support this fully then i guess we will have to go down the multiple server route. http://www.magentocommerce.com/product/enterprise-edition seemed to make out you could control things on a website level
      singulars
      1. PO
      1. USChris Hopkins
    2. COThere are some things that you can control on a website level (e.g. have different settings per website), but not everything. This is especially an issue if I read you correctly in that there will be multiple clients.
      singulars
      1. PO
      1. USJoseph Mastey
    3. COYes we will definitely be have multiple clients. Can I ask what experience / information you are basing your answer on?
      singulars
      1. PO
      1. USChris Hopkins
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload