Thread

I’ve got a website with 200 entries and 120ish columns in the data table. I’m going to have around 10 duplicates of this site in different languages with unique content for each. So if I was going to use MSM as it is currently configured, i’d have thousands of entries in the data table and over a thousand columns in that table as well.

It seems like it wouldn’t be that big of a deal to change the MSM so it uses separate databases instead of combining all of them into just 1.

Any ideas or suggestions?

Gary

Hi, Gary - This is not possible to do, you would need multiple installation to offer multiple databases.

200 entries really is nothing; what 120 columns are you talking about? The custom fields?  How many custom fields do you have on the one Site?

Have you considered any of the multi language options?

The 100ish columns are the custom fields. So each site has that many and each time it duplicates, it adds that many columns to the table. Is there any reason i should be concerned about having a table with over a thousand columns and a few thousand entries? Performance issues, etc?

I don’ think the multi-langauge idea will work, because each language will have unique content. So we have to have them on different sites.

Are there any plans on breaking the custom fields out into their own table in EE2? Seems like the data table could be better handled without all the empty columns for the custom fields.

Thanks

There are limits to the number of custom fields; that grew with 1.6.5 but it is still not limitless.

What are the 100 custom fields holding?  I think you can almost certainly re-think this infrastructure to come up with a more sane and stable setup, needing fewer custom fields means less maintenance and more scalability.

Otherwise you might need to group your sites into logical groupings with EE and MSM, and have a few installations with several Sites.