Upgrading v1.4004 to v2.0


https://forum.kartris.com/Topic1858.aspx
Print Topic | Close Window

By Neil - Sat 16 Mar 2013
Hi, I have got v2 running locally with our skin etc (all working well) and am planning to upgrade our db (v1.4004) to try it out. Can I use 'UpdateSQL_1.4000_To_2.000.sql' in the resources folder to do this?

Edit 1: Stuff it, I'm going to try it anyway. will report back.

Edit 2: SQL ran with the following result -


(4 row(s) affected)
Caution: Changing any part of an object name could break scripts and stored procedures.

(263 row(s) affected)
Caution: Changing any part of an object name could break scripts and stored procedures.

(149941 row(s) affected)
The module '_spKartrisCategories_Delete' depends on the missing object 'dbo._spKartrisProducts_DeleteByCategory'. The module will still be created; however, it cannot run successfully until the object exists.
The module '_spKartrisCategories_Delete' depends on the missing object 'dbo._spKartrisPromotions_DeleteByParent'. The module will still be created; however, it cannot run successfully until the object exists.
Msg 207, Level 16, State 1, Procedure _spKartrisLogins_Add, Line 36
Invalid column name 'LOGIN_PushNotifications'.
Msg 207, Level 16, State 1, Procedure _spKartrisLogins_GetList, Line 20
Invalid column name 'LOGIN_PushNotifications'.
Msg 207, Level 16, State 1, Procedure _spKartrisLogins_Update, Line 43
Invalid column name 'LOGIN_PushNotifications'.
The module '_spKartrisProducts_Delete' depends on the missing object 'dbo._spKartrisVersions_DeleteByProduct'. The module will still be created; however, it cannot run successfully until the object exists.
The module '_spKartrisProducts_Delete' depends on the missing object 'dbo._spKartrisPromotions_DeleteByParent'. The module will still be created; however, it cannot run successfully until the object exists.
The module '_spKartrisUsers_Delete' depends on the missing object 'dbo._spKartrisUsers_DeleteOrders'. The module will still be created; however, it cannot run successfully until the object exists.

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

(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)
By Paul - Sun 17 Mar 2013
You need to run any other incremental scripts in order.

For example, if your current version is 1.4001, then you need to run any minor updates on that such as 1.4001-1.4002, before running the major 1.4->2.0 script.
By Neil - Sun 17 Mar 2013
We are on 1.4004 which appears to be the last 1.4 release? I can see no scripts to go from here?
By Paul - Mon 18 Mar 2013
Does your db end up with those sprocs it says are missing? I think the major version -> major version update scripts clear out all old sprocs and replace with new (safest way to bring everything up to date). I haven't seen the issue when I've run the upgrades, and if we're wiping all sprocs and then create anew, every dependency issues with sprocs should be the same.

Does your db end up with those sprocs it says are missing?
By Neil - Wed 20 Mar 2013
Hi Paul, I just tried this again on my office computer and got the same result. I manually checked and all the sprocs it says are missing are actually there. I am going to try and get this db to connect.