Upgrading from 2.0.3 to 2.4.2

Added by Scott Hildebrand almost 5 years ago

Right now I'm using Redmine 2.0.3 and I'd like to upgrade to a newer version. I found it pretty easy to set up Redmine on Webfaction, and migrating the database was simple via phpMyAdmin. So my question is, what version of Redmine can I go up to using the current database from 2.0.3? Is the schema the same all the way up to 2.4.2 and can I use that?

Replies (5)

RE: Upgrading from 2.0.3 to 2.4.2 - Added by Ivan Cenov almost 5 years ago

There is differences in database schema between 2.0.3 and 2.4.2 You may see that from source:/tags/2.0.3/db/migrate and source:/tags/2.4.2/db/migrate. There is more files in the latter directory. However this should not be problem. Database migration is part of Redmine upgrading process. The command is (in Windows OS)

rake db:migrate RAILS_ENV=production
You also have to check compatibility of the plugins with the new version.

RE: Upgrading from 2.0.3 to 2.4.2 - Added by Scott Hildebrand almost 5 years ago

Could you please explain some more how to migrate the database? It's going from 2.0.3 on a Linux server to 2.4.2 on a Linux server.

RE: Upgrading from 2.0.3 to 2.4.2 - Added by Scott Hildebrand almost 5 years ago

If I just do an export of data from the old Redmine, can I just run that SQL to import into the new Redmine? If database tables and column names haven't changed, then that would work right?

RE: Upgrading from 2.0.3 to 2.4.2 - Added by Ivan Cenov almost 5 years ago

There is a database migration script, that is part of Redmine software and this script comes with Ruby on Rails framework. You should not (must not) manipulate the database by hand by SQL commands, exports, imports etc. Instead you have to use this script (it is a rake task), see my previous post. You may also want to see http://www.redmine.org/projects/redmine/wiki/RedmineUpgrade to take shape how things are performed and in what order.

RE: Upgrading from 2.0.3 to 2.4.2 - Added by Alex Wilhelmy almost 5 years ago

Hi!

I did the same (1.3.2 --> 2.2.4). When importing the database - also via phpmyadmin - I chose the option "drop/create table" in phpmyadmin. Thus you are kind of (re-)creating the schema. You do not have to do any DDL in SQL - it's a five minutes work in phpmyadmin (depending on your database size)!

So after import you have the old schema and the rake db-migrate-stuff worked perfectly well to upgrade the schema.

Hope this helps.

Cheers

Alex

(1-5/5)