In an upgrade from 3.0.13 to 3.3.7, I'm getting some, seemingly minor, errors.
Here is the status report from the install...
00:00:00.249 - Upgrading to Version: 3.1.0
Error! (seeC:\Projects\GMR2\Providers\DataProviders\SqlDataProvider\03.01.00.log for more information)
00:00:01.562 - Upgrading to Version: 3.1.1
Error! (seeC:\Projects\GMR2\Providers\DataProviders\SqlDataProvider\03.01.01.log for more information)
00:00:02.265 - Upgrading to Version: 3.2.0
Success
00:00:02.296 - Upgrading to Version: 3.2.1
Success
00:00:02.327 - Upgrading to Version: 3.2.2
Success
00:00:02.343 - Upgrading to Version: 3.2.3
Error! (seeC:\Projects\GMR2\Providers\DataProviders\SqlDataProvider\03.02.03.log for more information)
00:00:06.436 - Upgrading to Version: 3.2.4
Success
00:00:06.483 - Upgrading to Version: 3.2.5
Success
00:00:06.530 - Upgrading to Version: 3.2.6
Success
00:00:06.561 - Upgrading to Version: 3.2.7
Success
00:00:06.561 - Upgrading to Version: 3.3.0
Success
00:00:06.576 - Upgrading to Version: 3.3.1
Success
00:00:06.608 - Upgrading to Version: 3.3.2
Success
00:00:06.670 - Upgrading to Version: 3.3.3
Error! (seeC:\Projects\GMR2\Providers\DataProviders\SqlDataProvider\03.03.03.log for more information)
00:00:06.764 - Upgrading to Version: 3.3.4
Success
00:00:06.764 - Upgrading to Version: 3.3.5
Success
00:00:06.905 - Upgrading to Version: 3.3.6
Success
00:00:06.998 - Upgrading to Version: 3.3.7
Success
3.1.0 ended in;
Error: Violation of PRIMARY KEY constraint 'PK_EventLogTypes'. Cannot insert duplicate key in object 'EventLogTypes'.
The statement has been terminated.
3.1.1 displayed no errors.
3.2.3 ended in;
Error: Violation of PRIMARY KEY constraint 'PK_EventLogTypes'. Cannot insert duplicate key in object 'EventLogTypes'.
The statement has been terminated.
3.3.3 displayed no errors.
My first instinct was to just truncate that table before the upgrade. Will this cause any long term problems? It didn't look like EventLogTypes held anything but constants.
Any other ideas on keeping this upgrade error free?
Thanks.