Safe way of Migrating 2.2.6 to 3.1.0
Dear Community,
Dear Countersoft,
as i failed completely running the upgrade-scripts for an upgrade von 2.2.6 to 3.1.0 i started researching and the only answers i've found so far mentioned problems/solutions/hacks. It did not seem, that any of the suggestions contains a "run this script to get your data from db-a (2.2.6) to db-b (3.1.0)"-solution.
We're using 2.2.6 for quite a while now, so we have a huge amount of data that we would need to take over for a migration. The question, obviously is now: Is there a safe way and how to manage that?
Many thanks for your answers in advance.
Best regards
Crea-Ue. Kirdar
Crea
· 1 |
|
Monday, January 19, 2009, 12:39:02 PM |
0
|
With Gemini 3.x we have introduced a new schema and security model. This makes the upgrade a bit complicated as the old 2.x database did not have constraints. This is why you have seen people who reported errors during the upgrade. These are not hacks, it is just removing redundant data. The best way to upgrade, in our optionion, is by backing up your database and running the SQL scripts. If you get an error then it is more than likely to do with data that is redundant and should be excluded. |
||||
|
0
|
Hi Mark, |
||||
|
0
|
I suggest reading the migration guide: http://countersoft.com/downloads/csfiles/CounterSoftGeminiv310Documentation.zip This gives you step by step instructions on how to upgrade. Basically run:
Is that what you have done? |
||||
|
0
|
Thanks again! |
||||
|
0
|
Yes, it shows exactly what to do with duplicate types etc... |
||||
|
0
|
Hi Mark, |
||||
|