<?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: AMC Tables question - Best practices on maintaining? in Installing and Upgrading</title>
    <link>https://community.qlik.com/t5/Installing-and-Upgrading/AMC-Tables-question-Best-practices-on-maintaining/m-p/2386196#M5417</link>
    <description>&lt;P&gt;The customer should define retention policies on the amount of AMC data they want to keep. &amp;nbsp;Based on those retention policies, you will write a simple DI job to either archive the old records or delete them. &amp;nbsp; This way the AMC tables will not grow beyond control. &amp;nbsp; Yes, for the graph to display fast in AMC, and be quick, you will want to control how much data is in those tables and whether the right indexes are there.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;The questions to ask are:&lt;/P&gt; 
&lt;P&gt;- What is the value of knowing that a particular task failed 2 years ago with a null pointer exception?&lt;/P&gt; 
&lt;P&gt;- What is the value of knowing that a job that you had 6 months ago took 2 hours longer to run? &amp;nbsp;Nowadays maybe it doesn't because it has been refactored multiple times.&lt;/P&gt; 
&lt;P&gt;- What is the value of knowing that a particular job failed everytime it was run for x number of days 6 months ago?&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;Very often, while these history data may provide some insights, the most important data are usually what happened in the last couple of weeks. &amp;nbsp;And thus, having answers to these questions will help define the retention policy.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;The customer will need to build jobs to clear down the AMC tables, and should also look at how they want to index the data in those tables. &amp;nbsp;Its is&amp;nbsp;allowed to add additional columns to the AMC tables to capture additional information. &amp;nbsp;Hence,&amp;nbsp;additional indexes will be needed for those additional columns.&lt;/P&gt;</description>
    <pubDate>Sun, 18 Jun 2017 03:07:37 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2017-06-18T03:07:37Z</dc:date>
    <item>
      <title>AMC Tables question - Best practices on maintaining?</title>
      <link>https://community.qlik.com/t5/Installing-and-Upgrading/AMC-Tables-question-Best-practices-on-maintaining/m-p/2386195#M5416</link>
      <description>&lt;P&gt;It's been observed that when setting up the AMC, it creates and uses some database tables (as relates to this question SQL Server is the database chosen to house). &amp;nbsp;The interaction between AMC and these tables includes creating them and writing to them, but does not include any maintenance - indexes, purging etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are there best practices for maintaining these tables that AMC uses?&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 09:37:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Installing-and-Upgrading/AMC-Tables-question-Best-practices-on-maintaining/m-p/2386195#M5416</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T09:37:10Z</dc:date>
    </item>
    <item>
      <title>Re: AMC Tables question - Best practices on maintaining?</title>
      <link>https://community.qlik.com/t5/Installing-and-Upgrading/AMC-Tables-question-Best-practices-on-maintaining/m-p/2386196#M5417</link>
      <description>&lt;P&gt;The customer should define retention policies on the amount of AMC data they want to keep. &amp;nbsp;Based on those retention policies, you will write a simple DI job to either archive the old records or delete them. &amp;nbsp; This way the AMC tables will not grow beyond control. &amp;nbsp; Yes, for the graph to display fast in AMC, and be quick, you will want to control how much data is in those tables and whether the right indexes are there.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;The questions to ask are:&lt;/P&gt; 
&lt;P&gt;- What is the value of knowing that a particular task failed 2 years ago with a null pointer exception?&lt;/P&gt; 
&lt;P&gt;- What is the value of knowing that a job that you had 6 months ago took 2 hours longer to run? &amp;nbsp;Nowadays maybe it doesn't because it has been refactored multiple times.&lt;/P&gt; 
&lt;P&gt;- What is the value of knowing that a particular job failed everytime it was run for x number of days 6 months ago?&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;Very often, while these history data may provide some insights, the most important data are usually what happened in the last couple of weeks. &amp;nbsp;And thus, having answers to these questions will help define the retention policy.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;The customer will need to build jobs to clear down the AMC tables, and should also look at how they want to index the data in those tables. &amp;nbsp;Its is&amp;nbsp;allowed to add additional columns to the AMC tables to capture additional information. &amp;nbsp;Hence,&amp;nbsp;additional indexes will be needed for those additional columns.&lt;/P&gt;</description>
      <pubDate>Sun, 18 Jun 2017 03:07:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Installing-and-Upgrading/AMC-Tables-question-Best-practices-on-maintaining/m-p/2386196#M5417</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-06-18T03:07:37Z</dc:date>
    </item>
  </channel>
</rss>

