<?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: Qlikview Upgrade in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Qlikview-Upgrade/m-p/1577184#M1290905</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;There is a really nice article on our Knowledgebase  you can start with: &lt;A href="https://support.qlik.com/articles/000047580" target="_blank"&gt;https://support.qlik.com/articles/000047580&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I also recommend you to search more in our Knwleadgebase, as there is a lot of useful information.&lt;BR /&gt;&lt;BR /&gt;Is always advise to test a new version on a development environment. It could be a virtual environment, but you cannot use the same Server license in both environment, so you would need a new license for the new environment.&lt;BR /&gt;&lt;BR /&gt;Kind regards</description>
    <pubDate>Tue, 07 May 2019 06:22:21 GMT</pubDate>
    <dc:creator>Albert_Candelario</dc:creator>
    <dc:date>2019-05-07T06:22:21Z</dc:date>
    <item>
      <title>Qlikview Upgrade</title>
      <link>https://community.qlik.com/t5/QlikView/Qlikview-Upgrade/m-p/1577167#M1290903</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We are using the Qlikview 11 version in our Organisation. We would like to upgrade our server as there is Only 1 server (Production Server) is being utilized for both development and consumption of reports. Current Production server RAM is 120 GB with 8-core processor.&lt;/P&gt;&lt;P&gt;QlikView Server resource (CPU/RAM) utilization is very high. There is a need to upgrade the resources.&lt;/P&gt;&lt;P&gt;Below are some other details.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Platform – QlikView 11.20 (45 Named Cal and 150 Doc Cal).&lt;/LI&gt;&lt;LI&gt;Database – Multiple SQL Servers, AX D365 and Excel Files&lt;/LI&gt;&lt;LI&gt;Around 30 final QlikView Applications.&lt;/LI&gt;&lt;LI&gt;Raw Data Size – Around 120 GB&lt;/LI&gt;&lt;LI&gt;we have created these reports for their internal users of different departments.&lt;/LI&gt;&lt;LI&gt;All Named and Doc Cals are getting actively utilized by all the users with concurrency of around 15-20 users&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Can you please let us know the best practice to upgrade our QlikView environments?&lt;/P&gt;&lt;P&gt;Do we really need to buy a new Test server with Enterprise edition or lower edition can also work in this case ?or it can be done with one new server and leasing a license from the Qlikview live&amp;nbsp;environment?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Himanshi Dubey&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Qlikview-Upgrade/m-p/1577167#M1290903</guid>
      <dc:creator>himanshi</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: Qlikview Upgrade</title>
      <link>https://community.qlik.com/t5/QlikView/Qlikview-Upgrade/m-p/1577184#M1290905</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;There is a really nice article on our Knowledgebase  you can start with: &lt;A href="https://support.qlik.com/articles/000047580" target="_blank"&gt;https://support.qlik.com/articles/000047580&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I also recommend you to search more in our Knwleadgebase, as there is a lot of useful information.&lt;BR /&gt;&lt;BR /&gt;Is always advise to test a new version on a development environment. It could be a virtual environment, but you cannot use the same Server license in both environment, so you would need a new license for the new environment.&lt;BR /&gt;&lt;BR /&gt;Kind regards</description>
      <pubDate>Tue, 07 May 2019 06:22:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Qlikview-Upgrade/m-p/1577184#M1290905</guid>
      <dc:creator>Albert_Candelario</dc:creator>
      <dc:date>2019-05-07T06:22:21Z</dc:date>
    </item>
    <item>
      <title>Re: Qlikview Upgrade</title>
      <link>https://community.qlik.com/t5/QlikView/Qlikview-Upgrade/m-p/1585681#M1290911</link>
      <description>&lt;P&gt;Himanshi,&lt;/P&gt;
&lt;P&gt;This part stood out to me the most in your post:&lt;/P&gt;
&lt;P&gt;"&lt;SPAN&gt;&lt;STRONG&gt;QlikView Server resource (CPU/RAM) utilization is very high&lt;/STRONG&gt;. There is a need to upgrade the resources."&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Are you upgrading to try to resolve the high resource usage issue or are you upgrading to take advantage of the many bug fixes and performance improvements since your version of Qlikview 11.20 was released?&amp;nbsp; I would recommend getting your current environment stable before upgrading.&amp;nbsp; It's possible that upgrading COULD resolve your high resource usage, but more likely you'll need to figure out what's causing the high resource usage.&amp;nbsp; Have you opened a case with Qlik Support?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks,&lt;BR /&gt;Josh&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Qlik Support&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 May 2019 14:30:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Qlikview-Upgrade/m-p/1585681#M1290911</guid>
      <dc:creator>Josh_Berg_Support</dc:creator>
      <dc:date>2019-05-28T14:30:36Z</dc:date>
    </item>
    <item>
      <title>Re: Qlikview Upgrade</title>
      <link>https://community.qlik.com/t5/QlikView/Qlikview-Upgrade/m-p/1595333#M1290915</link>
      <description>&lt;P&gt;I just wanted to comment on the 'concurrency' statement regarding your Named and Document CALs, those do not have concurrency, so I am providing link below which covers the license agreement regarding Named and Doc CALs, so you can be sure you are not violating the use of those CALs.&amp;nbsp; Named and Doc CALs are to be 'permanently' assigned to a user until that user leaves the company or changes positions within the company no longer needing access to the product, any manipulation of the CALs to reassign users regularly is a violation of the product terms as per the document attached to the following link:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.qlik.com/us/-/media/files/legal/license-agreements/qlikview/qlikview-license-metrics-en.pdf?la=en" target="_blank"&gt;https://www.qlik.com/us/-/media/files/legal/license-agreements/qlikview/qlikview-license-metrics-en.pdf?la=en&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Each user needs to have their own Named or Doc CAL assigned to them....&lt;/P&gt;
&lt;P&gt;Here is the part of the pdf from the link above I want to be sure you understand:&lt;/P&gt;
&lt;P&gt;C. Identified Users&lt;BR /&gt;To use a Named User CAL or Document CAL, the user must be identified via an authenticated user name (Windows Active&lt;BR /&gt;Directory or through a ticket exchange between the web server and QlikView Server). The two methods of identification cannot be mixed on the same QlikView Server. An IP address is not a valid form of user identification. Note that the user name identification requires Windows authentication on AJAX clients, since machine name identification cannot be used for these clients.&lt;/P&gt;
&lt;P&gt;Named and Document CALs are assigned to an identified user and may not be transferred to another user unless the transfer is due to a i) termination of employment, or ii) a transfer of the user to a new business unit or group resulting in no access to the Qlik Software. When a Named User or Document CAL is transferred, there is a 7-day quarantine before the CAL can be used by another user.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Brett&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jun 2019 22:12:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Qlikview-Upgrade/m-p/1595333#M1290915</guid>
      <dc:creator>Brett_Bleess</dc:creator>
      <dc:date>2019-06-24T22:12:29Z</dc:date>
    </item>
  </channel>
</rss>

