<?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: Promotion of 3rd party libraries in SAS 9.4 in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Promotion-of-3rd-party-libraries-in-SAS-9-4/m-p/819584#M24592</link>
    <description>&lt;P&gt;I am guessing at what you may want to achieve here. If it is what I think and you are in the process of migrating your SAS deployment from 9.4M5 to M7 then yes: export the library metadata in M5 management console to an SPK file and import that in the M7 server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;NOTE: there can, as you mentioned, be related objects (servers, accounts, authentication domains, users, groups, tables, ACT's etc) that you need to take into account as well before everything will work as expected.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you have tables registered in your metadata it will usually work better to first export/import the library definitions and after that the tables in a separate step.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;/P&gt;
&lt;P&gt;- Jan.&lt;/P&gt;</description>
    <pubDate>Wed, 22 Jun 2022 12:12:50 GMT</pubDate>
    <dc:creator>jklaverstijn</dc:creator>
    <dc:date>2022-06-22T12:12:50Z</dc:date>
    <item>
      <title>Promotion of 3rd party libraries in SAS 9.4</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Promotion-of-3rd-party-libraries-in-SAS-9-4/m-p/819546#M24588</link>
      <description>&lt;P&gt;Hello Experts,&lt;/P&gt;
&lt;P&gt;I'm trying to understand how to promote a library for 3rd party database (be it any DB) from SAS 9.4M5 to SAS9.4M7.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it just enough to import them as we do for a Base SAS library, after importing system metadata and their respective database servers (and configurations at OS level)?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;or&lt;/P&gt;
&lt;P&gt;are there any additional steps required?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance, hope someone could help me understand this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jun 2022 07:56:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Promotion-of-3rd-party-libraries-in-SAS-9-4/m-p/819546#M24588</guid>
      <dc:creator>SASWayne</dc:creator>
      <dc:date>2022-06-22T07:56:40Z</dc:date>
    </item>
    <item>
      <title>Re: Promotion of 3rd party libraries in SAS 9.4</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Promotion-of-3rd-party-libraries-in-SAS-9-4/m-p/819584#M24592</link>
      <description>&lt;P&gt;I am guessing at what you may want to achieve here. If it is what I think and you are in the process of migrating your SAS deployment from 9.4M5 to M7 then yes: export the library metadata in M5 management console to an SPK file and import that in the M7 server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;NOTE: there can, as you mentioned, be related objects (servers, accounts, authentication domains, users, groups, tables, ACT's etc) that you need to take into account as well before everything will work as expected.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you have tables registered in your metadata it will usually work better to first export/import the library definitions and after that the tables in a separate step.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;/P&gt;
&lt;P&gt;- Jan.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jun 2022 12:12:50 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Promotion-of-3rd-party-libraries-in-SAS-9-4/m-p/819584#M24592</guid>
      <dc:creator>jklaverstijn</dc:creator>
      <dc:date>2022-06-22T12:12:50Z</dc:date>
    </item>
    <item>
      <title>Re: Promotion of 3rd party libraries in SAS 9.4</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Promotion-of-3rd-party-libraries-in-SAS-9-4/m-p/819598#M24594</link>
      <description>&lt;P&gt;Just to add, any exteral configuration files needs to be migrated as well, like ODBC DSN definitions, Oracle tsnames etc.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jun 2022 12:40:13 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Promotion-of-3rd-party-libraries-in-SAS-9-4/m-p/819598#M24594</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2022-06-22T12:40:13Z</dc:date>
    </item>
    <item>
      <title>Re: Promotion of 3rd party libraries in SAS 9.4</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Promotion-of-3rd-party-libraries-in-SAS-9-4/m-p/819856#M24596</link>
      <description>&lt;P&gt;Yes, the process is much the same as for SAS libraries. You would need to ensure that your SAS/ACCESS products have been correctly configured and tested on M7 prior to using the migrated library definitions. I find it useful to test each connection using an equivalent LIBNAME statement to ensure it is correctly configured.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jun 2022 23:28:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Promotion-of-3rd-party-libraries-in-SAS-9-4/m-p/819856#M24596</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2022-06-22T23:28:19Z</dc:date>
    </item>
  </channel>
</rss>

