You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Updating the crowd.cfg.xml file is not the right way to do what you want to do.
Here is a link to Atlassian's documentation regarding Crowd migration to another database: https://confluence.atlassian.com/crowd/migrate-to-another-database-180290495.html
So here is what you must do:
A bit of a late reply, but hopefully this might help others too. While the XML option is what's documented, we've done numerous database migrations in the past for Crowd between mysql > mysql and later psql > psql (standard dump and restore) and updated the connector in the crowd.cfg.xml file and the process worked well. Given it's easier to script a DB dump - we use this then push offsite as part of our DR/BC process.