<?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: Difference between Generic ODBC Access Engine versus Vendor Specific Access Engine in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Difference-between-Generic-ODBC-Access-Engine-versus-Vendor/m-p/360790#M8694</link>
    <description>&lt;P&gt;The ODBC ACCESS engine uses the standardized ODBC layer to connect to a database; this removes the necessity for SAS to know the specifics of the DBMS. On the machine in question, you only need the ODBC driver of the DBMS.&lt;/P&gt;
&lt;P&gt;With ACCESS to Relational Databases for MySQL, you need the DBMS client installed and configured. But you have the luxury that SAS can make better use of DBMS-specific capabilities when doing implicit pass-through.&lt;/P&gt;</description>
    <pubDate>Tue, 23 May 2017 15:19:32 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2017-05-23T15:19:32Z</dc:date>
    <item>
      <title>Difference between Generic ODBC Access Engine versus Vendor Specific Access Engine</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Difference-between-Generic-ODBC-Access-Engine-versus-Vendor/m-p/360775#M8692</link>
      <description>&lt;P&gt;Good Afternoon&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm trying to understand the difference between the generic SAS ACCESS/ODBC Engine and that or the Vendor specific ACCESS engine. In this case MySQL. Any guidance would be very much appreciated.&lt;/P&gt;</description>
      <pubDate>Tue, 23 May 2017 15:03:22 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Difference-between-Generic-ODBC-Access-Engine-versus-Vendor/m-p/360775#M8692</guid>
      <dc:creator>KeithCostigan</dc:creator>
      <dc:date>2017-05-23T15:03:22Z</dc:date>
    </item>
    <item>
      <title>Re: Difference between Generic ODBC Access Engine versus Vendor Specific Access Engine</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Difference-between-Generic-ODBC-Access-Engine-versus-Vendor/m-p/360790#M8694</link>
      <description>&lt;P&gt;The ODBC ACCESS engine uses the standardized ODBC layer to connect to a database; this removes the necessity for SAS to know the specifics of the DBMS. On the machine in question, you only need the ODBC driver of the DBMS.&lt;/P&gt;
&lt;P&gt;With ACCESS to Relational Databases for MySQL, you need the DBMS client installed and configured. But you have the luxury that SAS can make better use of DBMS-specific capabilities when doing implicit pass-through.&lt;/P&gt;</description>
      <pubDate>Tue, 23 May 2017 15:19:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Difference-between-Generic-ODBC-Access-Engine-versus-Vendor/m-p/360790#M8694</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2017-05-23T15:19:32Z</dc:date>
    </item>
    <item>
      <title>Re: Difference between Generic ODBC Access Engine versus Vendor Specific Access Engine</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Difference-between-Generic-ODBC-Access-Engine-versus-Vendor/m-p/360805#M8696</link>
      <description>&lt;P&gt;Thank you Kurt, very much appreciated.&lt;/P&gt;</description>
      <pubDate>Tue, 23 May 2017 15:38:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Difference-between-Generic-ODBC-Access-Engine-versus-Vendor/m-p/360805#M8696</guid>
      <dc:creator>KeithCostigan</dc:creator>
      <dc:date>2017-05-23T15:38:11Z</dc:date>
    </item>
  </channel>
</rss>

