1. General


1.1. You can only upgrade the system to newer versions (as usually), downgrade is not possible.

1.2. Upgrade to be done in 3 steps:

1.2.1. Upgrade files and working folders of all applications (servers).

1.2.1.1. This step also needs settings in files to be updated with new format. Use compare with manual and examples from distributive to define possible values.

1.2.2. Upgrade database

1.2.3. Upgrade translation

1.2.4. Upgrade licensing

1.3. You must stop all GK3 modules before upgrade procedures.

1.4. You must backup both modules and database before upgrade procedures. Copy folders to backup location (make archive) only during all modules are stopped (not running).

1.5. Think about clean up your accumulative DB with deletion of previous year's data before upgrade if necessary.


2. Upgrade applications


2.1. Take .exe, .dll files from new version distributive and replace your current version.

2.2. Take care of your settings (.ini files). Do not loose settings with totally overwritten them.


3. Upgrade DB


3.1. There are scripts in new version distributive which made to make changes in GK3 DB.

3.1.1. You may find those files in folder \sql\, each in separate folder named as [version from]-[version to], as well as in \Upgrade\ and \CopyData\ folders.

3.1.1.1. So, if you have for example DB version 3.15 now and want to upgrade to 3.19, you have to execute scripts 315-316.sql, 316-317.sql, 317-318.sql, 318-319.sql one by one. How to execute them read below.

3.1.1.1.1. You repeat steps 3.6-3.7 from part 3 below until you apply all necessary DB version changes.

3.1.1.1.2. You cannot apply only 318-319 step in case your DB current version is not 3.18. You must apply all steps mentioned above to make your DB version fit upgrade script that you are going to execute.

3.1.1.2. 'Upgrade' set of scripts will make new DB structure for you.

3.1.1.3. 'CopyData' will copy records from your old DB to new one.

3.1.1.3.1. Old DB may have huge amount of data and copy process will take a lot of time.

3.1.1.3.2. In case you get 'Command timeout' error, set bigger 'CMDTIMEOUT' parameter value (seconds, default =300).

3.1.2. Your current DB version you may get from database itself using query

SELECT * FROM gkArcade.dbo.SYS_VERSION_INFO where PRODUCT_ID = 'DBFILE'

3.1.3. You need to do steps 3.2-3.5. only in case your current DB version is <3.06. If your DB version >3.06 follow only steps 3.6-3.7 from part 3 below.

3.2. Copy file gk3.make from folder \Upgrade\ to folder \sql\.

3.2.1. Check parameters inside to fit your installation (set) and edit them if necessary.

3.3. Run gk3Install.bat.

3.3.1. If you got no errors (Script completed successfully), go on.

3.3.2. If you got errors, fix their roots and re-run.

3.4. Copy to \sql\ folder files CopyData.* (all extentions) from folder \CopyData\.

3.4.1. Check parameters inside CopyData.make file to fit your installation (set) and edit them if necessary.

3.5. Run CopyData.bat.

3.5.1. Make sure you got no errors (Script completed successfully).

3.5.2. If you got errors, fix their roots and re-run.

3.6. Copy to \sql\ folder files named with versions difference (3xx-3yy.*), for example 315-316.* (all extentions), from folder named as the same versions difference (3xx-3yy).

3.6.1. Check parameters inside *.make file named as versions difference (3xx-3yy.make) to fit your installation (set) and edit them if necessary.

3.7. Run .bat file named as current versions difference (3xx-3yy.bat).

3.7.1. Make sure you got no errors (Script completed successfully).

3.7.2. If you got errors, fix their roots and re-run.

3.8. You can execute those .sql scripts for upgrade with MSSQLMS instead.