<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: QV Bug Fix Environment Best practices in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/QV-Bug-Fix-Environment-Best-practices/m-p/1814485#M1245983</link>
    <description>&lt;P&gt;HI,&amp;nbsp;&lt;/P&gt;&lt;P&gt;couple of things here,&amp;nbsp;&lt;/P&gt;&lt;P&gt;1, QV server edition should be same across all environments. ( Hardware &amp;amp; Data volumes may only differ)&amp;nbsp;&lt;/P&gt;&lt;P&gt;2, It is not at all recommended to apply bugfix directly on prod server.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Major risk cases would be,&amp;nbsp;&lt;/P&gt;&lt;P&gt;indefinite downtime ( if anything went wrong) , Business impact (may leads to penalty incase of&amp;nbsp; support project) and uninstall &amp;amp; reinstall Qv server.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Apply fix on Dev environment first to test the bugfix issue and assess the impact.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;** Take necessary server backups before applying any fix&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;hope this helps,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sasi&lt;/P&gt;</description>
    <pubDate>Fri, 11 Jun 2021 12:51:59 GMT</pubDate>
    <dc:creator>sasikanth</dc:creator>
    <dc:date>2021-06-11T12:51:59Z</dc:date>
    <item>
      <title>QV Bug Fix Environment Best practices</title>
      <link>https://community.qlik.com/t5/QlikView/QV-Bug-Fix-Environment-Best-practices/m-p/1814455#M1245980</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I am looking for advice on the “Best Practices” for setting up different environments in Qlikview and where those environments should live.&lt;/P&gt;&lt;P&gt;We have two Separate servers.&amp;nbsp; One Production server and one Development server.&amp;nbsp;&amp;nbsp; On the Development server we have –&lt;/P&gt;&lt;P&gt;Development&lt;/P&gt;&lt;P&gt;UAT&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the Production Server we have –&lt;/P&gt;&lt;P&gt;Production&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And we have Bug Fix.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our issue is that our infrastructure and compliance team feels that Bug Fix should not be on the Production server.&amp;nbsp; They argue that if a QV developer does something ‘bad’ it could bring down the Production server.&lt;/P&gt;&lt;P&gt;On the other side, the QV team wants an environment that is as close to production as possible (there could be differences from Production and Development such as QV versions).&amp;nbsp; Having Bug Fix on the Production server allows them to quickly tests and address issues (Bugs).&lt;/P&gt;&lt;P&gt;Can anyone add thoughts on this as far as the risk of having a Bug Fix environment on the Production server?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank You,&lt;/P&gt;&lt;P&gt;Brian&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QV-Bug-Fix-Environment-Best-practices/m-p/1814455#M1245980</guid>
      <dc:creator>Brip51</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: QV Bug Fix Environment Best practices</title>
      <link>https://community.qlik.com/t5/QlikView/QV-Bug-Fix-Environment-Best-practices/m-p/1814485#M1245983</link>
      <description>&lt;P&gt;HI,&amp;nbsp;&lt;/P&gt;&lt;P&gt;couple of things here,&amp;nbsp;&lt;/P&gt;&lt;P&gt;1, QV server edition should be same across all environments. ( Hardware &amp;amp; Data volumes may only differ)&amp;nbsp;&lt;/P&gt;&lt;P&gt;2, It is not at all recommended to apply bugfix directly on prod server.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Major risk cases would be,&amp;nbsp;&lt;/P&gt;&lt;P&gt;indefinite downtime ( if anything went wrong) , Business impact (may leads to penalty incase of&amp;nbsp; support project) and uninstall &amp;amp; reinstall Qv server.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Apply fix on Dev environment first to test the bugfix issue and assess the impact.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;** Take necessary server backups before applying any fix&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;hope this helps,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sasi&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jun 2021 12:51:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QV-Bug-Fix-Environment-Best-practices/m-p/1814485#M1245983</guid>
      <dc:creator>sasikanth</dc:creator>
      <dc:date>2021-06-11T12:51:59Z</dc:date>
    </item>
    <item>
      <title>Re: QV Bug Fix Environment Best practices</title>
      <link>https://community.qlik.com/t5/QlikView/QV-Bug-Fix-Environment-Best-practices/m-p/1814609#M1245985</link>
      <description>&lt;P&gt;Hi Sasi,&lt;/P&gt;&lt;P&gt;Yes.&amp;nbsp; This doe help.&amp;nbsp; Thank you for your input.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Brian&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jun 2021 20:21:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QV-Bug-Fix-Environment-Best-practices/m-p/1814609#M1245985</guid>
      <dc:creator>Brip51</dc:creator>
      <dc:date>2021-06-11T20:21:53Z</dc:date>
    </item>
  </channel>
</rss>

