Page 1 of 1

Few errors upgrading to GOLD R9 from 7.0.3

Posted: Sun Nov 16, 2014 10:45 am
by meer2005
Ran into a few errors upgrading from 7.0.3 to GOLD R9. The upgrade finished, and everything seems to function, although sometimes seems sluggish, especially in admin. This was just and we'd like to go live in the next few days. We did it twice, once cleaning up the transaction log prior to upgrade. Both databases function, but we'd like to start off without any errors.


First try:

SQL: IF NOT EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLE_CONSTRAINTS WHERE TABLE_NAME = 'ac_CategoryParents' AND CONSTRAINT_NAME = 'ac_Categories_ac_CategoryParents_FK1') BEGIN ALTER TABLE "ac_CategoryParents" ADD CONSTRAINT ac_Categories_ac_CategoryParents_FK1 FOREIGN KEY ( CategoryId) REFERENCES ac_Categories ( CategoryId) ON UPDATE NO ACTION ON DELETE CASCADE END

Error: The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "ac_Categories_ac_CategoryParents_FK1". The conflict occurred in database "ACR9-gold-test", table "dbo.ac_Categories", column 'CategoryId'.
The database has been upgraded.

Second try:

this one I had to start over because the page errors

The errors listed below occurred while upgrading the database:
SQL: ALTER TABLE "ac_CategoryParents" DROP CONSTRAINT "ac_CategoryParents_PK"

Error: 'ac_CategoryParents_PK' is not a constraint. Could not drop constraint. See previous errors.

SQL: IF NOT EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLE_CONSTRAINTS WHERE TABLE_NAME = 'ac_CategoryParents' AND CONSTRAINT_NAME = 'ac_Categories_ac_CategoryParents_FK1') BEGIN ALTER TABLE "ac_CategoryParents" ADD CONSTRAINT ac_Categories_ac_CategoryParents_FK1 FOREIGN KEY ( CategoryId) REFERENCES ac_Categories ( CategoryId) ON UPDATE NO ACTION ON DELETE CASCADE END

Error: The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "ac_Categories_ac_CategoryParents_FK1". The conflict occurred in database "ACR9-goldtest2", table "dbo.ac_Categories", column 'CategoryId'.
The database has been upgraded.

Re: Few errors upgrading to GOLD R9 from 7.0.3

Posted: Mon Nov 17, 2014 4:22 am
by jmestep
I think we have seen similar errors in every Able 7 to Gold upgrade we have done, but like you say, everything seems to function. For performance problems, you could see if you have Lucene search turned on. If so, it could be running the initial indexing for that that is taking the time. If you have a great number of orders and the admin dashboard is slow, we have seen slow load times because of the recent orders display. You could also recycle the app pool right after the upgrade.

Re: Few errors upgrading to GOLD R9 from 7.0.3

Posted: Tue Nov 18, 2014 8:48 am
by meer2005
Lucene is not turned on, it's set to SQL. It seems better now, but initial server response time is still a bit sluggish. When doing a Google Site Speed test, server response item is flagged. Server response time was never an issue with 7.0.3.

Re: Few errors upgrading to GOLD R9 from 7.0.3

Posted: Mon Nov 24, 2014 8:08 am
by AbleMods
I've seen the same thing coming from older Able 7.x databases. Hasn't created any issues so far as I can tell.

If the site doesn't have active traffic, it's going to be sluggish because IIS needs a chance to compile and cache the pages that are hit. Subsequent hits to the same page should be much faster.

If the site is active, start with looking at total records in ac_Users. If it's high ( > 150,000), consider running SQL Profiler and Database Tuning Wizard to see what performance recommendations are available. I've seen DTW make a huge impact of all aspects of site speed with some Able sites.

Able Gold is a bigger app than Able 7.x. Expect it to take more RAM and CPU as a result. A borderline server for Able 7.x will most likely appear weak trying to run Able Gold.