CiviCRM Community Forums (archive)

I haven’t done it on a production server, but I think I once or twice did create a CiviCRM database from a common Drupal+CiviCRM one.

Basically, you should dump the database to a file, copy it to a second file, and then leave all the civicrm_* tables related content in one while removing it from the other. You can then import the two files as your new CiviCRM and Drupal databases.

Could I get some guidance on this?  I recently tried to do this dump and restore cycle in order to change servers, but I always get errors and it fails.  It complains about the "DEFAULT CHARSET=utf8" part of the commands.  So I edited the sql file to remove those phrases, but it failed again on some other part of the sql.  Is there a recipe somewhere for how to backup and restore?  Any suggestions welcome.

While my test went perfectly, when I ran the same procedure on the production site it wouldn't use the new Drupal db. The new CiviCRM db is fine. So I just left the appropriate settings pointed to the original db. Now I'd like to clean up and drop the civicrm tables which are not being used in the Drupal db. Somehow, I wasn't surprised when I got the following when I tried to drop civicrm_acl

ERROR 1217 (23000): Cannot delete or update a parent row: a foreign key constraint fails

Is there a particular order I should drop them? All at once? or can I tell it to ignore foreign key constraints somehow?

BTW upgraded test to 1.8 (with split db) flawlessly. Hope production is as smooth 

Neil

Thanks, I'll give it a try.
The 1.8 upgrade went great! CiviCRM 1.8 is really sweet!
After 8 months with a couple of hundred newbie users on http://www.greenparty.ca
I was especially pleased to find "Site Preferences" under "Global Settings" 

Lots of other goodies too.

http://www.voteformmp.ca is almost ready for prime time.
Server's waiting for more RAM and disk, and still some forms etc. to finish up and CiviMail, CiviEvent ...

Neil