<?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 LASR table name standards in SAS Visual Analytics</title>
    <link>https://communities.sas.com/t5/SAS-Visual-Analytics/LASR-table-name-standards/m-p/457984#M10003</link>
    <description>&lt;P&gt;Hello everyone, I am in process of loading our first set of datasets into LASR tables from our SQL Server registered tables library.&amp;nbsp; I have been watching some of SAS video's and based on my reading on some of the blogs mostly adding and LASR extension&amp;nbsp;to the name of LASR.&amp;nbsp; For example if my table name called T_Employee in LASR they name it T_Employee LASR.&amp;nbsp; Is there any reason for it and if I don't use a LASR would it be an issue in the future?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your assistant&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 26 Apr 2018 22:51:22 GMT</pubDate>
    <dc:creator>L2Fly</dc:creator>
    <dc:date>2018-04-26T22:51:22Z</dc:date>
    <item>
      <title>LASR table name standards</title>
      <link>https://communities.sas.com/t5/SAS-Visual-Analytics/LASR-table-name-standards/m-p/457984#M10003</link>
      <description>&lt;P&gt;Hello everyone, I am in process of loading our first set of datasets into LASR tables from our SQL Server registered tables library.&amp;nbsp; I have been watching some of SAS video's and based on my reading on some of the blogs mostly adding and LASR extension&amp;nbsp;to the name of LASR.&amp;nbsp; For example if my table name called T_Employee in LASR they name it T_Employee LASR.&amp;nbsp; Is there any reason for it and if I don't use a LASR would it be an issue in the future?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your assistant&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Apr 2018 22:51:22 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Visual-Analytics/LASR-table-name-standards/m-p/457984#M10003</guid>
      <dc:creator>L2Fly</dc:creator>
      <dc:date>2018-04-26T22:51:22Z</dc:date>
    </item>
    <item>
      <title>Re: LASR table name standards</title>
      <link>https://communities.sas.com/t5/SAS-Visual-Analytics/LASR-table-name-standards/m-p/457987#M10004</link>
      <description>&lt;P&gt;Personally I can't see the point of renaming a table when loading it into LASR. Adding LASR as a suffix on LASR table name looks completely redundant to me as you can identify all LASR tables by the SAS library they are in.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have a practice of preparing our LASR tables in a normal SAS library first, which we refer to as our LASR Staging library. Then we keep exactly the same table names when we load them into LASR. To me this a simple and obvious approach - changing table names unless there is a good business reason seems pointless. I can understand you would want to have different names if the table contents were different, for example if you were doing update-type loads rather than replacement-type loads, but if your load and LASR tables are identical I suggest keeping the names the same is good practice.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Apr 2018 23:11:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Visual-Analytics/LASR-table-name-standards/m-p/457987#M10004</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2018-04-26T23:11:11Z</dc:date>
    </item>
    <item>
      <title>Re: LASR table name standards</title>
      <link>https://communities.sas.com/t5/SAS-Visual-Analytics/LASR-table-name-standards/m-p/457989#M10005</link>
      <description>&lt;P&gt;Thank you &lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/13976"&gt;@SASKiwi&lt;/a&gt;&amp;nbsp;for your help and info.&amp;nbsp; Much appreciated, the way I have ours setup is to using ODBC library straight to our DW and registered all of tables we want users to access from EG or SAS Studio.&amp;nbsp; Then based on the business requirement I am moving some of these tables into LASR to be used by our users in visual analytics.&amp;nbsp; I am assuming you "your LASR staging" is the same as my ODBC library.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Again thanks for the info.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Apr 2018 23:25:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Visual-Analytics/LASR-table-name-standards/m-p/457989#M10005</guid>
      <dc:creator>L2Fly</dc:creator>
      <dc:date>2018-04-26T23:25:30Z</dc:date>
    </item>
  </channel>
</rss>

