In the use case of having a standalone-installation of the repository database (hosting the Postgres repository database on a separate server), the resiliance to lost/dropped connections is not as good as cases where the database is installed on the same machine. The resiliency of Qlik Sense to losing database connectivity should be improved for this use case.Environment:
- Qlik Sense Enterprise, 3.2 and higher
- Remotely-hosted Repository Database
When Repository Database is hosted separately, Qlik Sense has same stability to lost connections as when the Repository Database is hosted locally.Actual Behavior:
When the connection is lost to the database, such as stopping the database service before shutting down the repository service, instable behavior is observed in Qlik Sense.
The current recommendation is to shut down all other Qlik Sense services before shutting down the repository database (and conversely, to start the database first and then the rest of the Qlik Sense services).Qlik has previously received feedback on this feature and recorded the request for future review. For up to date information, please contact support at (support.qlik.com) referencing this article.