Upgrade Procedure for SQL Reporting Solutions

The upgrade procedure for SQL Reporting involves upgrading the databases followed by upgrading the reports. These procedures are detailed in this topic.

Upgrading the Databases

Upgrade 11.9 on the Reporting Server to the latest version

Copy the files 'Setup.defaults' and 'SetupReports.defaults' from the deployed '<product>' folder into the new 'Solutions/<product> folder.


Server\Configuration> copy BigDataInsight\UC\*.defaults BigDataInsight\Solutions\UC

Close any windows (e.g. file explorer) that are using the folder <Prognosis Home>\Server\Configuration\BigDataInsight\<product>.

Failure to do so will result in the upgrade failing.

Start a Command Prompt with 'Run as Administrator' and change to the following setup folder path:

<Prognosis Home>\Server\Configuration\BigDataInsight\Solutions\<product>

Run the command:

> setup.bat

The setup will ask a series of questions that are used to upgrade the SQL Reporting solution. The same settings as used previously should be re-used. These settings are stored in the 'Setup.defaults' file.

Please provide a name to uniquely identify this deployment of the <product> model.

Deployment Name (Default: <product>) >

Enter the name of the deployment and then press <Enter>. This must match the name of what was previously deployed. The default deployment name is the name of the product (e.g. UC).

A reporting solution named <deployment name> had previously been deployed.

If you wish to create an additional deployment then quit now then provide a new deployment name.

Continuing will alter/upgrade this deployment.

Would you like to [C]ontinue or [Q]uit?

Press <Enter> to continue the configuration (using the default option of 'C' to Continue).

Enter the SQL Server instance name on 'SQL Server' (Default: 'Your default instance name') <Enter>.

Enter the Datamart database name (Default: 'Your existing datamart DB') <Enter>.

Enter the Staging database name (Default: 'Your existing staging/source DB') <Enter>.

The specified databases are not empty and are different to the version currently being setup.

Deployed version: 11.*.*
Setup version: 11.*.*

You can:
[U]pgrade Prognosis Insight
[D]elete the databases and create new ones,
[M]odify the database names used as part of this deployment,
or [Q]uit.

[U]pgrade [D]elete [M]odify [Q]uit
(Default: U)>

Press <Enter> to confirm the database upgrade (using the default option of 'U' to Upgrade).

It is strongly recommended that the BigDataInsight<product>Source and BigDataInsight<product> databases be backed up before continuing with the upgrade.
Failure to do so may result in data loss, if there are any issues with the upgrade.

Are you ready to proceed with the upgrade now?
[Y]es or [N]o (Default: N)>

Confirm that you wish to proceed, having created a backup, by entering 'Y'.

Enter 'How many months of data should be kept for reporting' (Default: 'Existing aging') <Enter>.

Enter the nodes to collect from, use comma separated list or use 'default' for all nodes (Default: #AllNodes) <Enter>.

Add the SSIS Server hostname/IP address (Default: 'Your existing SSIS Server')> <Enter>.

Add the SSIS Server instance name on 'SSIS Server' (Default: 'Your default instance name')> <Enter>.

Enter the full path where the SSIS package is going to be deployed (Default: 'Your existing folder on SSIS Server'):> <Enter>.

Enter the login password for the user ('setup user name'):> <your password> <Enter> (twice).

Continue with these settings ? [C]ontinue [M]odify [Q]uit (Default: C)> <Enter>

Next, it will be necessary to follow the steps at the end of the setup process. These must be completed manually, follow the instructions carefully from the setup output:

If instructed, copy the SSIS folder to the SSIS/SQL server (replacing the SSIS directory that used to be on the server) Take careful note of the paths displayed. It will be necessary to copy the deployment SSIS folder from the deployment folder e.g. <Prognosis_Home>\Server\Configuration\BigDataInsight\<product> rather than the setup folder <Prognosis_Home>\Server\Configuration\BigDataInsight\Solutions\<product>

Copy any customized csv files from the deployment folder backup to the following folder path:


If using the SQL Server Agent to schedule the ETL:

a)   Re-enable the ETL job that was disabled during the install.

b)   Re-configure SQL Reporting to not run the ETL itself. For details see Scheduling the ETL Job via the SQL Server.

Following an upgrade, monitor the system to ensure that the ETL jobs are running successfully. Refer to Scheduling the ETL Job via the SQL Server for further details. If the ETL jobs are failing, ensure that any SSIS files setup instructed to copy to the SSIS server have been copied

Additional Manual Steps

In certain scenarios during an upgrade, there may be a prompt to manually run an ETL.

Choose 'Y' to ensure that all the data from the Staging database is moved into the Datamart database before upgrading.

Please run an ETL manually, to avoid data loss
Have you successfully run an ETL manually?

[Y]es or [N]o (Default: N)

Upgrade Reports

After the 'Upgrade' steps have been completed, deploy the updated reports by following the process outlined in the Install the SQL Reports on the SSRS Server. When prompted “Overwrite existing reports?”   Type 'Y' for Yes.

Provide feedback on this article