<?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 Data Migration in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/SAS-Data-Migration/m-p/558264#M155794</link>
    <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/51337"&gt;@vijayanand&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There is no CDC for SAS tables. You would need to implement fully blown ETL delta processing which is nothing you can just do on-the-fly as an intermediary measure.&lt;/P&gt;
&lt;P&gt;Best you can do is to compress/zip your data before transferring from source to target - but you will still need to transfer the whole file.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;...or: Any chance to map the file system used by the old server also to the new server as an intermediary measure?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 13 May 2019 11:40:35 GMT</pubDate>
    <dc:creator>Patrick</dc:creator>
    <dc:date>2019-05-13T11:40:35Z</dc:date>
    <item>
      <title>SAS Data Migration</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Data-Migration/m-p/558253#M155791</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We recently have migrated some SAS data sets from Unix server to Linux server. The data sets which were migrated already, are growing daily (some observations are being added,some are being updated and some are being deleted) on the source server (Unix).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How do we bring all these changes alone on to the target (Linux Server).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Some of the data sets are very hugs in size, so migrating the entire data set again from source to target is very time consuming and this has to happen daily , till the target server goes live.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Vijay.&lt;/P&gt;</description>
      <pubDate>Mon, 13 May 2019 10:56:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Data-Migration/m-p/558253#M155791</guid>
      <dc:creator>vijayanand</dc:creator>
      <dc:date>2019-05-13T10:56:25Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Data Migration</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Data-Migration/m-p/558264#M155794</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/51337"&gt;@vijayanand&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There is no CDC for SAS tables. You would need to implement fully blown ETL delta processing which is nothing you can just do on-the-fly as an intermediary measure.&lt;/P&gt;
&lt;P&gt;Best you can do is to compress/zip your data before transferring from source to target - but you will still need to transfer the whole file.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;...or: Any chance to map the file system used by the old server also to the new server as an intermediary measure?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 May 2019 11:40:35 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Data-Migration/m-p/558264#M155794</guid>
      <dc:creator>Patrick</dc:creator>
      <dc:date>2019-05-13T11:40:35Z</dc:date>
    </item>
  </channel>
</rss>

