<?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 Can partitioning help to increase responsiveness of a VA report? in SAS Visual Analytics</title>
    <link>https://communities.sas.com/t5/SAS-Visual-Analytics/Can-partitioning-help-to-increase-responsiveness-of-a-VA-report/m-p/988688#M18978</link>
    <description>&lt;P&gt;In our reports we make an extensive use of filters and parameters and derived actions from one object on others.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It works fine in terms of response time if, code-wise, I create a subset of the whole main table. To give you an idea, this might reduce the row count from 3.5 millions to&amp;nbsp; 200.000 as our main filter criteria is the plant.&lt;/P&gt;
&lt;P&gt;We suffice with one unique report built with tables that live in caslibs that are accessible for all authorized report users. We control what they can see (plant bound) with the&amp;nbsp;cas action&amp;nbsp;&lt;STRONG&gt;accessControl.updSomeAcsTable&lt;/STRONG&gt;. That works but it comes at the cost that the report is very slow sometimes.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So I wonder if partitioning the table by plant would be a promising solution to explore.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 27 May 2026 09:05:59 GMT</pubDate>
    <dc:creator>acordes</dc:creator>
    <dc:date>2026-05-27T09:05:59Z</dc:date>
    <item>
      <title>Can partitioning help to increase responsiveness of a VA report?</title>
      <link>https://communities.sas.com/t5/SAS-Visual-Analytics/Can-partitioning-help-to-increase-responsiveness-of-a-VA-report/m-p/988688#M18978</link>
      <description>&lt;P&gt;In our reports we make an extensive use of filters and parameters and derived actions from one object on others.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It works fine in terms of response time if, code-wise, I create a subset of the whole main table. To give you an idea, this might reduce the row count from 3.5 millions to&amp;nbsp; 200.000 as our main filter criteria is the plant.&lt;/P&gt;
&lt;P&gt;We suffice with one unique report built with tables that live in caslibs that are accessible for all authorized report users. We control what they can see (plant bound) with the&amp;nbsp;cas action&amp;nbsp;&lt;STRONG&gt;accessControl.updSomeAcsTable&lt;/STRONG&gt;. That works but it comes at the cost that the report is very slow sometimes.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So I wonder if partitioning the table by plant would be a promising solution to explore.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 May 2026 09:05:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Visual-Analytics/Can-partitioning-help-to-increase-responsiveness-of-a-VA-report/m-p/988688#M18978</guid>
      <dc:creator>acordes</dc:creator>
      <dc:date>2026-05-27T09:05:59Z</dc:date>
    </item>
  </channel>
</rss>

