Qlik Community

Knowledge

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements
Support Case Portal has moved to Qlik Community! Read the FAQs to start exploring Support resources.

How to configure Qlik Sense to use a dedicated PostgreSQL database

Sebastian_Linser

How to configure Qlik Sense to use a dedicated PostgreSQL database

Or: How to move Qlik Sense database to a standalone PostgreSQL server?

The Qlik Sense Repository Database (QSR) can be moved to a dedicated standalone PostgreSQL instance not hosted on the same machine as other Qlik Sense Services. It is also possible to move an already existing QSR from a local Sense install, to a dedicated PostgresSQL database.

Environment

 

Set up a postgresSQL database

Instructions for this might vary slightly. Please refer to the Qlik Online Help for details.  We recommend watching this video.

Qlik Sense Enterprise server has a set of five databases. For more details visit Installing and configuring PostgreSQL on help.qlik.com.

1. The Qlik Sense repository database (QSR):

The QSR is the primary database in your Qlik Sense deployment.

2. The Qlik Sense services database (SenseServices):

The SenseServices database contains schemas for each of the Qlik Sense services and allows growth independently of the Qlik Sense Repository Database, while still sharing the same PostgreSQL instance and login role.

3. The Qlik Sense message queue database (QSMQ):

The QSMQ database provides a light-weight method of passing messages internally between services in Qlik Sense Enterprise. The NOTIFY and LISTEN functionality in PostgreSQL allows services to be notified about new messages that have been written to the messaging table.

4. The Qlik Sense logging database (QLogs):

The QLogs database centralizes logging by collecting log messages from all Qlik Sense nodes in your deployment and stores them in a PostgreSQL database.

5. The Qlik Sense license service database (Licenses):

The QLogs database centralizes logging by collecting log messages from all Qlik Sense nodes in your deployment and stores them in a PostgreSQL database.


 

Simplified checklist of steps:

  1. Download a valid version of postgresSQL.  For Sense June 2017 and up, 9.6.x is required, from November 2019 version 11.5.x as well.  Review the system requirements of your version before proceeding.
  2. Install based on instructions found on the Qlik Online Help for Qlik Sense; select the version you are running on then select from Menu , Deploy - Qlik Sense installation - Installing and configuring PostgreSQL.
Examples:

 

Moving the Qlik Sense Share Folders as well?

Follow How to change the shared path in Qlik Sense 

Backup 

Depending on the version, you need to backup different databases, on the current Qlik Sense central node hosting the Qlik Sense Repository Database service, follow the backup instructions to obtain a database copy of each Qlik Sense Database Present . 
   Example for February 2021  you need to backup the databases reported in section "Installing and configuring PostgreSQL"; referring to the Help site these are : 
    QSR , QSMQ , SenseServices , Licenses , if configured QLogs    

Restore

On the dedicated remote postgresSQL host, perform a restore   of the backed up Databases of previous point. 

Changing the Connection String to QSR and QSMQ Database 

  1. On the Qlik Sense central node, all services but the Qlik Sense Repository Service are shut down.
  2. Open QlikSenseUtil. By default, this will be installed in: C:\Program Files\Qlik\Sense\Repository\Util\QlikSenseUtil\QlikSenseUtil.exe
  3. Open the Connection String Editor and Read the current configuration, decrypting the current data.

    Sebastian_Linser_0-1615898800179.png
  4. Replace all mentions of the current database hostname.  In our example, the new database resides on 172.16.16.103. Instead of an IP you can also use the FQDN of the db server.
  5. You need to repeat this step for the   sections <add name="QSMQ" and <add name="postgres"
  6. Hit Save Value in config file encrypted, committing any changes. 

 

Sebastian_Linser_1-1615898853355.png

 

Changing the Connection String to SenseServices Databases. 

       Execute steps in Moved Postgress database to new host, but some qliksense is still accessing the SenseServices old da...; check if different version of article are present for different Qlik Sense version .

Changing the Connection String to Licenses Database ( April 2019 and up ) 

Starting from April 2019 new License Service implementation is using this database.

  1.   Open an elevated Powershell and change directory to C:\Program Files\Qlik\Sense\Licenses
  2.    Run the script .\Configure-Service.ps1 and provide:
    • new Hostname or IP  
    • database port default is 4432
    • database user qliksenserepository
    • databasepassword is the qliksenserepository password  used during configuration of  the new database.
  3. example: 
  4. cd  'C:\Program Files\Qlik\Sense\Licenses'
  5. .\Configure-Service.ps1 172.16.16.102 4432 qliksenserepository Password123!

It will look like this:

Windows PowerShell
Copyright (C) 2014 Microsoft Corporation. All rights reserved.

PS C:\Windows\system32> cd \
PS C:\> cd  'C:\Program Files\Qlik\Sense\Licenses'
PS C:\Program Files\Qlik\Sense\Licenses> .\Configure-Service.ps1 172.16.16.102 4432 qliksenserepository Password123!
Licenses configuration started.
WARNING: Skipping the database initialization. No superuser or password specified.
Reading the settings file.
Saving the modified settings.
Licenses configuration successful.
PS C:\Program Files\Qlik\Sense\Licenses>


repeat this for:

C:\Program Files\Qlik\Sense\NotifierService\install\Configure-Service.ps1
C:\Program Files\Qlik\Sense\AppDistributionService\Configure-Service.ps1
C:\Program Files\Qlik\Sense\HybridDeploymentService\Configure-Service.ps1
C:\Program Files\Qlik\Sense\MobilityRegistrarService\install\Configure-Service.ps1
C:\Program Files\Qlik\Sense\PrecedentsService\install\Configure-Service.ps1
C:\Program Files\Qlik\Sense\NLAppSearch\install\Configure-Service.ps1

there might come new services or disappear with new releases, please check in the C:\Program Files\Qlik\Sense\ folder for "Configure-Service.ps1" to find additional one in your version of Qlik Sense.

Update the Qlik Logging Service Connection String     

If the QLogs needs to be update you could check on help.qlik.com the section "Updating the connection string parameters" providing new hostname or ip. 

Remove Database Service dependency and Postgres Server ( to avoid issues with future Upgrade of Environment)

Qlik Sense Repository service dependency on the Database service needs to be removed and Database needs to be removed. 

In an elevated command prompt, execute the following on prompt:

c:\sc config "QlikSenseRepositoryService" depend= ""
c:\sc config "QlikLoggingService" depend= ""

This should return: 

[SC] ChangeServiceConfig SUCCESS

Restart the Qlik Sense Repository Service.

Check that Qlik Sense Repository Database doesn't start (confirms [SC] ChangeServiceConfig SUCCESS ).

Remove the (local) Qlik Sense Repository Database

Find the most recent PostgreSQL.msi in C:\ProgramData\Package Cache\  and remove it. This removes the service but no old local database data. This is needed to prevent issues on future upgrades of Environment.
You can find the precise folder with this command:

c:\cd ProgramData\Package Cache
c:\ProgramData\Package Cache\dir /s PostgreSQL.msi

The folder containing PostgreSQL.msi will be revealed.
Right click on the PostgreSQL.msi file and select uninstall from the menu.
    

Finalize

  1. Restart the Qlik Sense Repository Service and check that Qlik Sense Repository Database doesn't start (confirms [SC] ChangeServiceConfig SUCCESS )
  2. Start all remaining Sense Services 
  3. Progress on the startup sequence (including the connection to the new database) can be tracked in the _System_Repository log files located in C:\ProgramData\Qlik\Sense\Log\Repository\Trace
  4. Verify functionality.
  5. In Multi-node scenario you need to repeat steps "Changing the Connection Strings to Databases" on all Rim nodes; if required and configured "Update the Qlik Logging Service Connection String" .   

  6. This article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Labels (3)
Version history
Revision #:
8 of 8
Last update:
‎2021-09-22 10:52 AM
Updated by: