Update LS Insight from v. 2022.3 to v. 2023.1

If you have set up version 2022.3 of LS Insight, you can apply the changes in version 2023.1 by downloading the update package and running the script against your current LS Insight instance.

Note: The Azure Data Factory containing the ETL process pipelines will be replaced and some of the stored procedures in the DW database will be updated, so if you have made any customizations to the pipelines or stored procedures in the DW database, you should make sure that you have information about all those changes since they might be overwritten.

Note: This update includes updates for Scheduler job and pre-staging tables for Info codes, Special groups, and Family code.

Tip: If you have a large number of customizations, we recommend that you set up a new LS Insight instance with new DW and ADF beside the older instance of LS Insight, and move your customizations between them before you start using the new instance.

Download update

You can download the update package from our Azure storage.

Preparation

Before you run the Update script you need to disable the Scheduled Run trigger in the LS Insight instance you want to update. If you view the instructions on how to activate the trigger, you can follow those, but this time you set Activated to No and then apply and publish the changes.

Update LS Insight

  1. Open the update package folder you just downloaded, in VS Code.
    • To open the whole folder in VS Code, you open it in File Explorer and then right-click in a whitespace, not a file, and select Open with Code.
  2. Open the UpdateLSInsight.ps1 script in VS Code, and run by clicking F5.
  3. The script will first ask if you have access to the file path to the parameter file (Parameters.json) that is located in the LS Insight project folder that was created when LS Insight was deployed (YYYYMMDDHHMM-MyProject).
    • If you still have access to the project folder, you can reuse the parameters by answering Yes and providing the full path to the Parameters.json file.
    • If the project folder has been removed or deleted, you just answer No and enter the parameters when prompted.
      Note: You need to use the same parameters you supplied when you installed LS Insight. You can find the connection parameters and the names of your current SQL server, database, and Azure data factory in the Azure portal.
  4. The script then prompts for Azure subscription ID and login to Azure.
  5. Next, the script collects the parameters that have not been set, and validates connection parameters to LS Central and LS Insight.
  6. The script now runs the updates.
    • This update applies all changes described in the Data Warehouse section of the release notes to the existing LS Insight data warehouse and pipelines.
    • Since there are column updates in LS Central the the update will drop all staging tables and recreate them. This can have the affect that the next scheduled run takes longer than usual to complete.
    • If you have a LS Central SaaS the update will also create prestaging tables for new source tables that have been added in this version.
  7. When the script has finished running, it displays a message.

Post update

When the script is done, if you have added any extension tables, you need to review the LSInsight$SourceTableMap and make sure that the tables you have added have the correct name with a prefix.

Everyone must then go back to the Azure portal and manually run the Populate Query Base pipeline to update staging tables with the additional columns.

You also need to start the Scheduled run trigger again, and verify that it is still set to the time and timezone you want.
Note: Remember to publish after you have reactivated the trigger.

If there are new pre-staging tables added by the update script, there should also be a new Scheduler Job Header file included in the update package. Once the update is done, you need to import the changes through LS Import Export WS in LS Central. In the import, you can choose whether to override existing sub and scheduler jobs or not.

If you choose not to “overwrite existing”, your subjob and Scheduler jobs will stay as they are, but the new jobs will be added to the Scheduler jobs. Even if you overwrite subjobs that have been added to Scheduler jobs will not be deleted.

If you choose to overwrite, all changes you have made will be overwritten by the settings in the new file, where by default all subjobs in the Scheduler jobs are enabled.

Note: If an action subjob is added, you must run the preaction job with only the new subjobs enabled.