Qlik Sense November 2018 - PostgreSQL 9.6 - Windows Server 2016

[ilias_fytrakis]

Dear all,

I would like to get a clarification about Qlik Sense Nov.2018 and PostgreSQL 9.6 running on Windows Server 2016. The documentation states that Microsoft Windows Server 2016 is a certified platform for November 2018 version. (URL: https://help.qlik.com/en-US/sense/November2018/Subsystems/PlanningQlikSenseDeployments/Content/Sense...). On the other hand, in PostgreSQL documentation, version 9.6 is certified up to 2012 R2. (URL: https://www.postgresql.org/download/windows/).

How should we proceed in a Qlik Sense installation on Windows Server 2016, in order to be fully certified? Should we install PostgreSQL v.10 - v.11 and use this for hosting the Qlik Sense system repositories or should we use the bundled version?

Thanks in advance for any answers.

Best regards,

Ilias

[Giuseppe_Novello]

I would think, this only matter when Qlik Sense software is what you installing, this you got out QA/approval from out system requirements what we do support in a Windows 2016 ( regardless if we use PostgreSQL 9.6 for our database). I would assume this is more if this refer by separating the PostgreSQL DB and Qlik Sense architecture ( like the Multinode large example listed here : https://help.qlik.com/en-US/sense/February2019/Subsystems/PlanningQlikSenseDeployments/Content/Sense... )

However, I have dealt with customer with this implementation with Windows 2016 and they are working perfectly fine.  

[Levi_Turner · Accepted solution]

Yes, this is a current gap (PostgreSQL 9.6 does not officially support Windows 2016). Our R&D organization are working on testing Qlik Sense against more modern versions of PostgreSQL. The likely delivery would be official support for standalone  newer versions then a later delivery of an upgraded instance bundled with Qlik Sense.

Practically for a supportability standpoint for Qlik, we support Windows 2016, full stop.

[ilias_fytrakis]

Thank you both for your answers.

We have also deployed QS Nov.2018 on Windows Server 2016 and it works fine. We just wanted an official answer since we also spotted the gap.

Best regards,

Ilias