Hi,

I'm trying to update our Gemini installation from 2.2.6 to 3.0.4.

Per the Migration Guide, I execute

CreateTables.sql

CreateViews.sql

CreateProcs.sql

When I run CreateTables.sql, I get the following warnings…

Warning: The table 'geminicustomfielddefinitions' has been created but its maximum row size (8460) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

Warning: The table 'geminicustomfielddata' has been created but its maximum row size (8064) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

 

(1 row(s) affected)

 

Warning: The table 'geminicustomfielddefinitions' has been created but its maximum row size (8460) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

Warning: The table 'geminicustomfielddata' has been created but its maximum row size (8064) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

 

(1 row(s) affected)

 

 

(1 row(s) affected)

 

Warning: The table 'geminicustomfielddefinitions' has been created but its maximum row size (8460) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

 

(1 row(s) affected)

 

Warning: The table 'geminicustomfielddata' has been created but its maximum row size (8064) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

 

(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)

 

 

(2 row(s) affected)

 

Warning: The table 'geminicustomfielddefinitions' has been created but its maximum row size (8460) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

Warning: The table 'geminicustomfielddata' has been created but its maximum row size (8064) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

 

What is the impact of those warnings?

 

Disregarding the previous Warnings, I run Upgradev3-0-Step1.sql and get the following errors...

 

Server: Msg 547, Level 16, State 1, Line 219

INSERT statement conflicted with COLUMN FOREIGN KEY constraint 'geminiversionsprojectidfk'. The conflict occurred in database 'Gemini', table 'geminiprojects', column 'projectid'.

The statement has been terminated.

 

(0 row(s) affected)

 

Server: Msg 547, Level 16, State 1, Line 225

INSERT statement conflicted with COLUMN FOREIGN KEY constraint 'geminicomponentsprojectidfk'. The conflict occurred in database 'Gemini', table 'geminiprojects', column 'projectid'.

The statement has been terminated.

 

(0 row(s) affected)

 

 

(23 row(s) affected)

 

 

(0 row(s) affected)

 

 

(0 row(s) affected)

 

 

(0 row(s) affected)

 

 

(1 row(s) affected)

 

 

(0 row(s) affected)

 

 

(0 row(s) affected)

 

 

(0 row(s) affected)

 

Server: Msg 547, Level 16, State 1, Line 260

INSERT statement conflicted with COLUMN FOREIGN KEY constraint 'geminiissuesversionidfk'. The conflict occurred in database 'Gemini', table 'geminiversions', column 'versionid'.

The statement has been terminated.

 

At this point, I go to my geminiissues table to validate that the issues have migrated, and I find 0 records. So it seems as if the previous errors are stopping the migration somehow because there are no issues in the gemini_issues table.

 

I continue updating with the second upgrade script, and then try to logon to Gemini. Things look ok, no exceptions or anything, but I have 0 issues in any of my projects. Ouch.

 

Any ideas? For obvious reasons I had to revert to my backup in order to maintain 2.2.6 functionality while I figure out why I can’t update to 3.0.4, so any help would be welcome as I would love to start using v3 and its new features.

 

Thanks,

Darren