Migrate to 3.3.5 from 2.2.7
Is there any way to migrate from 2.2.7 to 3.3.5 not using the upgrate SQL?
I have 2 sites; One running 2.2.7 and the other site 3.3.5
Can I import from the 2.2.7 to the 3.3.5?
I try on a test site to take the data from 2.2.7 and run the Upgrades but end up with a mess with users and issues and projects mix up and not showing.
Is there any ready made SQL queries for it (or a application)?
Thanks,
talbengal
· 1 |
|
Wednesday, July 29, 2009, 10:35:25 AM |
0
|
The best way to do this is by upgrading the 2.2.7 database to 3.5 and using the import app to import the issues from the upgraded database. |
||||
|
0
|
It say on the documentation
EXISTING USER ROLES/PERMISSIONS FROM 2.x RELEASE ARE NOT MIGRATED TO 3.x RELEASE. I do not want to upgrade the existing 2.2.7 ! Its working fin as it is and do not want to disturb the working environment. I want to migrate the data from it to the new 3.3.5 site.
|
||||
|
0
|
Yes, but you can take a backup of it migrate it and export the data from it to the new 3.5.3 database. |
||||
|
0
|
What about EXISTING USER ROLES/PERMISSIONS ? |
||||
|
0
|
On Upgradev3-0-Step1.sql getting this errors: (0 row(s) affected) Msg 515, Level 16, State 2, Line 36 Cannot insert the value NULL into column 'created', table 'GEMINI.dbo.geminierrorlog'; column does not allow nulls. INSERT fails. The statement has been terminated. (4 row(s) affected) (2 row(s) affected) Msg 515, Level 16, State 2, Line 48 Cannot insert the value NULL into column 'created', table 'GEMINI.dbo.geminiusers'; column does not allow nulls. INSERT fails. The statement has been terminated. (0 row(s) affected) Msg 547, Level 16, State 0, Line 204 The INSERT statement conflicted with the FOREIGN KEY constraint "geminiprojectsuseridfk". The conflict occurred in database "GEMINI", table "dbo.geminiusers", column 'userid'. The statement has been terminated. (0 row(s) affected) Msg 515, Level 16, State 2, Line 219 Cannot insert the value NULL into column 'created', table 'GEMINI.dbo.geminiversions'; column does not allow nulls. INSERT fails. The statement has been terminated. (0 row(s) affected) Msg 547, Level 16, State 0, Line 225 The INSERT statement conflicted with the FOREIGN KEY constraint "geminicomponentsprojectidfk". The conflict occurred in database "GEMINI", table "dbo.geminiprojects", column 'projectid'. The statement has been terminated. (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) Msg 547, Level 16, State 0, Line 251 The INSERT statement conflicted with the FOREIGN KEY constraint "geminiprojectversionattributevaluesattributeidfk". The conflict occurred in database "GEMINI", table "dbo.geminiprojectversionattributes", column 'attributeid'. The statement has been terminated. (0 row(s) affected) Msg 515, Level 16, State 2, Line 260 Cannot insert the value NULL into column 'estimateminutes', table 'GEMINI.dbo.geminiissues'; column does not allow nulls. INSERT fails. The statement has been terminated. 0 row(s) affected) Msg 547, Level 16, State 0, Line 415 The INSERT statement conflicted with the FOREIGN KEY constraint "geminiusesettingsuseridfk". The conflict occurred in database "GEMINI", table "dbo.gemini_users", column 'userid'. The statement has been terminated.
|
||||
|
0
|
Ok after correct all the NULL's Iam getting this errors running it again, can i ignor it? (62516 row(s) affected) (62516 row(s) affected) (27 row(s) affected) Msg 547, Level 16, State 0, Line 44 The DELETE statement conflicted with the REFERENCE constraint "geminiprojectsuseridfk". The conflict occurred in database "GEMINI", table "dbo.geminiprojects", column 'userid'. The statement has been terminated. Msg 2627, Level 14, State 1, Line 48 Violation of PRIMARY KEY constraint 'geminiuseriduseridpk'. Cannot insert duplicate key in object 'dbo.geminiusers'. The statement has been terminated. (0 row(s) affected) (11 row(s) affected) (6 row(s) affected) (10 row(s) affected) (17 row(s) affected) Msg 547, Level 16, State 0, Line 65 The DELETE statement conflicted with the REFERENCE constraint "geminiprojectsissuetypeschemeidfk". The conflict occurred in database "GEMINI", table "dbo.geminiprojects", column 'issuetypeschemeid'. The statement has been terminated. (14 row(s) affected) (4 row(s) affected) (1 row(s) affected) (1 row(s) affected) (1 row(s) affected) (1 row(s) affected) (1 row(s) affected) (1 row(s) affected) (1 row(s) affected) (1 row(s) affected) (1 row(s) affected) (1 row(s) affected) Msg 2627, Level 14, State 1, Line 88 Violation of PRIMARY KEY constraint 'geminiissuetypeschemesissuetypeschemeidpk'. Cannot insert duplicate key in object 'dbo.geminiissuetypeschemes'. The statement has been terminated. Msg 2627, Level 14, State 1, Line 89 Violation of PRIMARY KEY constraint 'geminiissuetypeschemesissuetypeschemeidpk'. Cannot insert duplicate key in object 'dbo.geminiissuetypeschemes'. The statement has been terminated. Msg 2627, Level 14, State 1, Line 90 Violation of PRIMARY KEY constraint 'geminiissuetypeschemesissuetypeschemeidpk'. Cannot insert duplicate key in object 'dbo.geminiissuetypeschemes'. The statement has been terminated. (14 row(s) affected) (1 row(s) affected) (1 row(s) affected) (1 row(s) affected) (7 row(s) affected) Msg 547, Level 16, State 0, Line 110 The DELETE statement conflicted with the REFERENCE constraint "geminiprojectsissuepriorityschemeidfk". The conflict occurred in database "GEMINI", table "dbo.geminiprojects", column 'issuepriorityschemeid'. The statement has been terminated. (7 row(s) affected) (4 row(s) affected) (1 row(s) affected) (1 row(s) affected) (1 row(s) affected) Msg 2627, Level 14, State 1, Line 125 Violation of PRIMARY KEY constraint 'geminiissuepriorityschemesissuepriorityschemeidpk'. Cannot insert duplicate key in object 'dbo.geminiissuepriorityschemes'. The statement has been terminated. (7 row(s) affected) (8 row(s) affected) Msg 547, Level 16, State 0, Line 135 The DELETE statement conflicted with the REFERENCE constraint "geminiprojectsissueseverityschemeidfk". The conflict occurred in database "GEMINI", table "dbo.geminiprojects", column 'issueseverityschemeid'. The statement has been terminated. (8 row(s) affected) (4 row(s) affected) (1 row(s) affected) (1 row(s) affected) (1 row(s) affected) (1 row(s) affected) Msg 2627, Level 14, State 1, Line 151 Violation of PRIMARY KEY constraint 'geminiissueseverityschemesissueseverityschemeidpk'. Cannot insert duplicate key in object 'dbo.geminiissueseverityschemes'. The statement has been terminated. (8 row(s) affected) (6 row(s) affected) (14 row(s) affected) (6 row(s) affected) (6 row(s) affected) (6 row(s) affected) (6 row(s) affected) (6 row(s) affected) (14 row(s) affected) (7 row(s) affected) (7 row(s) affected) (4 row(s) affected) (4 row(s) affected) Msg 547, Level 16, State 0, Line 202 The DELETE statement conflicted with the REFERENCE constraint "geminiprojectrepositoryprojectidfk". The conflict occurred in database "GEMINI", table "dbo.geminiprojectrepository", column 'projectid'. The statement has been terminated. Msg 2627, Level 14, State 1, Line 204 Violation of PRIMARY KEY constraint 'geminiprojectsprojectidpk'. Cannot insert duplicate key in object 'dbo.geminiprojects'. The statement has been terminated. (166 row(s) affected) (166 row(s) affected) (18 row(s) affected) (18 row(s) affected) (1 row(s) affected) (1 row(s) affected) (0 row(s) affected) (0 row(s) affected) (2 row(s) affected) (2 row(s) affected) (0 row(s) affected) Msg 547, Level 16, State 0, Line 251 The INSERT statement conflicted with the FOREIGN KEY constraint "geminiprojectversionattributevaluesattributeidfk". The conflict occurred in database "GEMINI", table "dbo.geminiprojectversionattributes", column 'attributeid'. The statement has been terminated. (0 row(s) affected) Msg 547, Level 16, State 0, Line 260 The INSERT statement conflicted with the FOREIGN KEY constraint "geminiissuesversionidfk". The conflict occurred in database "GEMINI", table "dbo.geminiversions", column 'versionid'. The statement has been terminated. (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (2 row(s) affected) (3 row(s) affected) (3 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (28 row(s) affected) (9 row(s) affected) (9 row(s) affected) (0 row(s) affected) (0 row(s) affected) (0 row(s) affected) (2 row(s) affected)
|
||||
|
0
|
SELECT * FROM gemini_issues give me no records ... |
||||
|
0
|
BED IDEA!! all this upgrade from 2.2.7 made the current 2.2.7 unstable and its falling over on all kind of issues!! Lest go back to my original question: IS THERE A WAY TO IMPORT FROM 2.2.7 site to 3.3.5 site? Do not want to upgrade the 2.2.7 site - it is distrapting a working environment!
|
||||
|
0
|
No. |
||||
|