https://community.qlik.com/t5/Talend-Studio/Indexes-on-log-tables-for-AMC/m-p/2288526#M62005 Hello, I am trying to take advantage of the AMC. We've been using the three Talend logging tables for a while, so they've grown quite large. Can someone tell me which columns on those tables should be indexed to improve performance of the AMC?<BR />Thanks,<BR />Jesse Thu, 24 Jan 2013 22:57:18 GMT Anonymous 2013-01-24T22:57:18Z https://community.qlik.com/t5/Talend-Studio/Indexes-on-log-tables-for-AMC/m-p/2288526#M62005 Hello, I am trying to take advantage of the AMC. We've been using the three Talend logging tables for a while, so they've grown quite large. Can someone tell me which columns on those tables should be indexed to improve performance of the AMC?<BR />Thanks,<BR />Jesse Thu, 24 Jan 2013 22:57:18 GMT https://community.qlik.com/t5/Talend-Studio/Indexes-on-log-tables-for-AMC/m-p/2288526#M62005 Anonymous 2013-01-24T22:57:18Z https://community.qlik.com/t5/Talend-Studio/Indexes-on-log-tables-for-AMC/m-p/2288527#M62006 Why are you wanting to retain the data "for a while"? What are you trying to accomplish? <BR />If you must retain AMC data, say for long term for historical reporting, then I suggest you roll off data from the Talend database into an archival or analytic database to maintain the runtime performance of you jobs that write to the AMC. <BR />You may find that indexing the AMC will slow your jobs as they now need to maintain the index. Fri, 25 Jan 2013 17:05:05 GMT https://community.qlik.com/t5/Talend-Studio/Indexes-on-log-tables-for-AMC/m-p/2288527#M62006 Anonymous 2013-01-25T17:05:05Z https://community.qlik.com/t5/Talend-Studio/Indexes-on-log-tables-for-AMC/m-p/2288528#M62007 that is why the AMC provides multiple connections<BR />you can have one for 'current' and another for 'historical' Mon, 28 Jan 2013 17:23:01 GMT https://community.qlik.com/t5/Talend-Studio/Indexes-on-log-tables-for-AMC/m-p/2288528#M62007 Anonymous 2013-01-28T17:23:01Z