We are planning to update the compose version from 7.0.0.651 to 2022.5.0.140(May2022). do we need to run any additional step or is it just straight forward upgrade process. Is there any documentation for the upgrade which I can follow?
2022.5.0.140 is initial release and is good to go with latest patch version which is sp01 and support team can share the download link on a support case.
Note : 7.0 is Gen1 and 2022.05 is Gen2 and both can run parallelly
Upgrade steps are as follows which is tried and tested:
1) Install latest patch version of May 2022 in the same server.
2) Copy the data folder (can ignore logs directory inside data) from 7.0 version (which will copy the license as well) to the May2022 install directory (program Files/Qlik/Compose/).
3) Open the command prompt navigate to program Files/Qlik/Compose/bin (may2022 install folder) and run the following command:
i) Composecli.exe connect
ii) Composecli.exe upgrade
4) And then run the following command which will create scripts (output provides the script location) which we have to execute directly on the DW Database:
Composecli.exe generate_update_scripts
5) Then restart the Qlik Compose windows service
6) Validate Database and Model.
7) To avoid recreating Datawarehouse/DM objects check the option Generate DDL but do not run them in Project settings and create the Datawarehouse. Generate the task statements and validate.
😎 Same goes for DM -> validate and Generate the statements.
9) Uncheck the project settings option "Generate DDL but do not run them"
10) Validate the Datawarehouse and DM again to make sure everything is good.
Although I agree with Shashi's steps, the official way of upgrading from 7.0.0.651 to 2022.5.0.140(May 2020) has to be done in 3 steps. Below are our release notes, and I would recommend that you follow these steps for a smooth upgrade process.
Upgrading from Compose for Data Warehouses 6.6.1 (September 2020) or 7.0 (November 2020):
You can download all the relevant software from our support community portal
a. Upgrade to Compose February 2021.
b. Upgrade to Compose May 2021. c. Compose May 2022.
2022.5.0.140 is initial release and is good to go with latest patch version which is sp01 and support team can share the download link on a support case.
Note : 7.0 is Gen1 and 2022.05 is Gen2 and both can run parallelly
Upgrade steps are as follows which is tried and tested:
1) Install latest patch version of May 2022 in the same server.
2) Copy the data folder (can ignore logs directory inside data) from 7.0 version (which will copy the license as well) to the May2022 install directory (program Files/Qlik/Compose/).
3) Open the command prompt navigate to program Files/Qlik/Compose/bin (may2022 install folder) and run the following command:
i) Composecli.exe connect
ii) Composecli.exe upgrade
4) And then run the following command which will create scripts (output provides the script location) which we have to execute directly on the DW Database:
Composecli.exe generate_update_scripts
5) Then restart the Qlik Compose windows service
6) Validate Database and Model.
7) To avoid recreating Datawarehouse/DM objects check the option Generate DDL but do not run them in Project settings and create the Datawarehouse. Generate the task statements and validate.
😎 Same goes for DM -> validate and Generate the statements.
9) Uncheck the project settings option "Generate DDL but do not run them"
10) Validate the Datawarehouse and DM again to make sure everything is good.
Although I agree with Shashi's steps, the official way of upgrading from 7.0.0.651 to 2022.5.0.140(May 2020) has to be done in 3 steps. Below are our release notes, and I would recommend that you follow these steps for a smooth upgrade process.
Upgrading from Compose for Data Warehouses 6.6.1 (September 2020) or 7.0 (November 2020):
You can download all the relevant software from our support community portal
a. Upgrade to Compose February 2021.
b. Upgrade to Compose May 2021. c. Compose May 2022.
As per our discussion on the support case yesterday, we tried the approach I suggested and upgrade was successful. Hence I marked the suggestion I gave as the accepted solution. Let's continue working on the support case.
