<?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 pre-assigned libraries and retaining metadata when joining tables in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/pre-assigned-libraries-and-retaining-metadata-when-joining/m-p/10252#M2602</link>
    <description>In Enterprise Guide if you query a SQL Server table in a pre-assigned library, the metadata attributes are retained to the resulting output dataset.&lt;BR /&gt;
But if you join two SQL Server tables, then the metadata attributes are -not- retained to the output dataset.&lt;BR /&gt;
&lt;BR /&gt;
Is there a way to enforce this ?&lt;BR /&gt;
&lt;BR /&gt;
Background:&lt;BR /&gt;
The registered library is pointing to a SQL Server database (via Access to OLEDB).&lt;BR /&gt;
This library is pre-assigned: in the metadata by the checkmark "Library is pre-assigend" and in the autoexec of the SASAPP server containing this line:&lt;BR /&gt;
libname cdw meta libid=A5JD5D6P.AZ000010;&lt;BR /&gt;
 &lt;BR /&gt;
On the registered tables in the library we changed some attributes like the label and formats on certain columns. &lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
Ebele</description>
    <pubDate>Thu, 09 Jun 2011 13:57:57 GMT</pubDate>
    <dc:creator>Ebele</dc:creator>
    <dc:date>2011-06-09T13:57:57Z</dc:date>
    <item>
      <title>pre-assigned libraries and retaining metadata when joining tables</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/pre-assigned-libraries-and-retaining-metadata-when-joining/m-p/10252#M2602</link>
      <description>In Enterprise Guide if you query a SQL Server table in a pre-assigned library, the metadata attributes are retained to the resulting output dataset.&lt;BR /&gt;
But if you join two SQL Server tables, then the metadata attributes are -not- retained to the output dataset.&lt;BR /&gt;
&lt;BR /&gt;
Is there a way to enforce this ?&lt;BR /&gt;
&lt;BR /&gt;
Background:&lt;BR /&gt;
The registered library is pointing to a SQL Server database (via Access to OLEDB).&lt;BR /&gt;
This library is pre-assigned: in the metadata by the checkmark "Library is pre-assigend" and in the autoexec of the SASAPP server containing this line:&lt;BR /&gt;
libname cdw meta libid=A5JD5D6P.AZ000010;&lt;BR /&gt;
 &lt;BR /&gt;
On the registered tables in the library we changed some attributes like the label and formats on certain columns. &lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
Ebele</description>
      <pubDate>Thu, 09 Jun 2011 13:57:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/pre-assigned-libraries-and-retaining-metadata-when-joining/m-p/10252#M2602</guid>
      <dc:creator>Ebele</dc:creator>
      <dc:date>2011-06-09T13:57:57Z</dc:date>
    </item>
    <item>
      <title>Re: pre-assigned libraries and retaining metadata when joining tables</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/pre-assigned-libraries-and-retaining-metadata-when-joining/m-p/10253#M2603</link>
      <description>This looks like the same problem we have. If it is, SAS Tech Support has confirmed that this is how it works. We find it quite irritating, and have requested that SAS makes it a priority to remedy the problem.&lt;BR /&gt;
&lt;BR /&gt;
If it's causing you grief as well, I suggest leaning on SAS as well. The more the merrier!&lt;BR /&gt;
&lt;BR /&gt;
Tom</description>
      <pubDate>Fri, 10 Jun 2011 00:38:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/pre-assigned-libraries-and-retaining-metadata-when-joining/m-p/10253#M2603</guid>
      <dc:creator>TomKari</dc:creator>
      <dc:date>2011-06-10T00:38:48Z</dc:date>
    </item>
  </channel>
</rss>

