If you are suggesting pointing two different versions of Confluence at the same database instance, the newer version of Confluence will upgrade the database schema and you will no longer be able to run the old version off of that database. If bad things happen, then your world begins to implode. :)
You can most likely create a second database instance on your existing database server. Unless it is already overloaded or low on disk space, there shouldn't any ill effect from doing this. It would be a good idea to have a different database user for the "dev" instance, though. This will prevent each version of Confluence from seeing the other's databases. You'll need to do a mysqldump of the data and load that in the new instance.
If you can't create another instance on the hosted database server, you can install MySQL on a local server, do a mysqldump of the hosted instance data and load your local database with the dump file. Point your "dev" instance of Confluence to that db and test your upgrade prior to upgrading the live "prod" data.
![Dave Theodore [Coyote Creek Consulting]](https://avatar-management--avatars.us-west-2.prod.public.atl-paas.net/initials/DT-5.png "Dave Theodore [Coyote Creek Consulting]"){kind=avatar}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.