Author Topic: Shared or Separate Databases (Read 645 times)

Interpolat · February 04, 2014, 07:01:46 pm

I have comfortably been setting up CiviCRM integrations with Worpdress for a while now, with the CRM and CMS each having their own separate database. I have found references explicitly recommending that the CRM and CMS databases be separated in Drupal integrations as well. However, I am having a hard time finding explicit recommendations one way or the other (whether to keep databases shared or separate) in the case of Joomla-CiviCRM integrations. I would appreciate some insight.

Thanks

Coleman Watts · February 04, 2014, 07:08:04 pm

I don't think CMS is much of a factor in that recommendation. Having separate databases is just all-around easier to manage.

Interpolat · February 06, 2014, 10:01:41 am

Thanks Coleman for response.

mcsmom · February 09, 2014, 04:15:27 pm

Actually, I think in Joomla it's more normal to keep them together. The installation process doesn't give you a way to link to a separate database so if you want to do that it requires some custom work. Of course if you are doing a lot of customizing anyway it doesn't matter. But you would definitely not be able to use the standard install script.

CiviCRM Community Forums (archive)

News:

Author Topic: Shared or Separate Databases (Read 645 times)

Interpolat

Shared or Separate Databases

Coleman Watts

Re: Shared or Separate Databases

Interpolat

Re: Shared or Separate Databases

mcsmom

Re: Shared or Separate Databases