When I install a new Relate 2.0 site from deployment center, it will put the CMS and Community tables in the same database. I want to separate them.
What I did now is to export all the pages from the combined database and import them into a fresh CMS database. This way the CMS database is clean of Community tables, but the Relate database is till containing CMS tables.
The ideal scenario would be if there was a way to change the install scripts so that I get to choose where to create the Community tables like when I install a new Community (not Relate) site.
When I install a new Relate 2.0 site from deployment center, it will put the CMS and Community tables in the same database. I want to separate them.
What I did now is to export all the pages from the combined database and import them into a fresh CMS database. This way the CMS database is clean of Community tables, but the Relate database is till containing CMS tables.
The ideal scenario would be if there was a way to change the install scripts so that I get to choose where to create the Community tables like when I install a new Community (not Relate) site.
Ideas?