<?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: Visual Analytics Sandbox in SAS Visual Analytics</title>
    <link>https://communities.sas.com/t5/SAS-Visual-Analytics/Visual-Analytics-Sandbox/m-p/308695#M5738</link>
    <description>&lt;P&gt;SAS VA doesn't have a special sandbox mode. A SAS VA installation is the same regardless of whether you use it for development work, production work or both together.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you did want to fully separate your production VA environment from your development VA one you would need to do this in your VA architectural design prior to installation. A typical approach would be to have two separate VA application servers. This would obviously come at a significant hardware and software cost.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you have only one VA application server then you could consider running two LASR servers on the same physical server, one for production and the other for development. You would have to carefully set memory limits so one didn't adversely affect the other.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Reports are stored in SAS metadata folders so you could have separate folders for production and development work. Moving the reports between the folders would have to be managed manually. VA doesn't currently contain functionality for change control.&lt;/P&gt;</description>
    <pubDate>Wed, 02 Nov 2016 07:39:59 GMT</pubDate>
    <dc:creator>SASKiwi</dc:creator>
    <dc:date>2016-11-02T07:39:59Z</dc:date>
    <item>
      <title>Visual Analytics Sandbox</title>
      <link>https://communities.sas.com/t5/SAS-Visual-Analytics/Visual-Analytics-Sandbox/m-p/308575#M5732</link>
      <description>&lt;P&gt;&amp;nbsp;We would like to be able to run a sandbox or parallel instance of VA so that we can test reports before rolling out to users.&amp;nbsp;Does VA have a sandbox mode? If not how do people handle updating datasets without "breaking" an exisiting report?&lt;/P&gt;</description>
      <pubDate>Tue, 01 Nov 2016 17:21:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Visual-Analytics/Visual-Analytics-Sandbox/m-p/308575#M5732</guid>
      <dc:creator>jrothermel</dc:creator>
      <dc:date>2016-11-01T17:21:28Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Analytics Sandbox</title>
      <link>https://communities.sas.com/t5/SAS-Visual-Analytics/Visual-Analytics-Sandbox/m-p/308695#M5738</link>
      <description>&lt;P&gt;SAS VA doesn't have a special sandbox mode. A SAS VA installation is the same regardless of whether you use it for development work, production work or both together.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you did want to fully separate your production VA environment from your development VA one you would need to do this in your VA architectural design prior to installation. A typical approach would be to have two separate VA application servers. This would obviously come at a significant hardware and software cost.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you have only one VA application server then you could consider running two LASR servers on the same physical server, one for production and the other for development. You would have to carefully set memory limits so one didn't adversely affect the other.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Reports are stored in SAS metadata folders so you could have separate folders for production and development work. Moving the reports between the folders would have to be managed manually. VA doesn't currently contain functionality for change control.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Nov 2016 07:39:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Visual-Analytics/Visual-Analytics-Sandbox/m-p/308695#M5738</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2016-11-02T07:39:59Z</dc:date>
    </item>
  </channel>
</rss>

