<?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: SAS DI Studio : lock table with check-in/check-out functionality in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/SAS-DI-Studio-lock-table-with-check-in-check-out-functionality/m-p/873400#M20714</link>
    <description>&lt;P&gt;I can understand the need at some level.&lt;/P&gt;
&lt;P&gt;But DI Studio is all about metadata, not "actual data".&lt;/P&gt;
&lt;P&gt;AFAIK there is no standard functionality that you can perform to make this happen linked to check-out/check-in.&lt;/P&gt;
&lt;P&gt;Also consider data in external datasets.&lt;/P&gt;
&lt;P&gt;So the question is, how big of problem is this? Maybe it can be solved via communication in the development teams?&lt;/P&gt;
&lt;P&gt;Also, locking down tables may halt other developers/testers that need to recreate the table for their job.&lt;/P&gt;
&lt;P&gt;What I can think of is that you create OS script to change authorizations for checked out scripts. But who will execute that?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 02 May 2023 15:17:44 GMT</pubDate>
    <dc:creator>LinusH</dc:creator>
    <dc:date>2023-05-02T15:17:44Z</dc:date>
    <item>
      <title>SAS DI Studio : lock table with check-in/check-out functionality</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SAS-DI-Studio-lock-table-with-check-in-check-out-functionality/m-p/873336#M20713</link>
      <description>&lt;P&gt;Hi all, in SAS DI Studio we are testing the functionality of check-in/check-out. We found out that when a table is checked-out a other user can still execute data processing (for example : load data with table loader) on this table. We would expect a lock mechanism or something similair.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How can we prevent data processing on a (database) table when this table is check-out in SAD DI Studio.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the advice, tips, .... etc&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 02 May 2023 11:08:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SAS-DI-Studio-lock-table-with-check-in-check-out-functionality/m-p/873336#M20713</guid>
      <dc:creator>JeroenPotgieter</dc:creator>
      <dc:date>2023-05-02T11:08:06Z</dc:date>
    </item>
    <item>
      <title>Re: SAS DI Studio : lock table with check-in/check-out functionality</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SAS-DI-Studio-lock-table-with-check-in-check-out-functionality/m-p/873400#M20714</link>
      <description>&lt;P&gt;I can understand the need at some level.&lt;/P&gt;
&lt;P&gt;But DI Studio is all about metadata, not "actual data".&lt;/P&gt;
&lt;P&gt;AFAIK there is no standard functionality that you can perform to make this happen linked to check-out/check-in.&lt;/P&gt;
&lt;P&gt;Also consider data in external datasets.&lt;/P&gt;
&lt;P&gt;So the question is, how big of problem is this? Maybe it can be solved via communication in the development teams?&lt;/P&gt;
&lt;P&gt;Also, locking down tables may halt other developers/testers that need to recreate the table for their job.&lt;/P&gt;
&lt;P&gt;What I can think of is that you create OS script to change authorizations for checked out scripts. But who will execute that?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 02 May 2023 15:17:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SAS-DI-Studio-lock-table-with-check-in-check-out-functionality/m-p/873400#M20714</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2023-05-02T15:17:44Z</dc:date>
    </item>
  </channel>
</rss>

