<?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: If access MS SQL data via SAS/Access to MS SQL , still need to edit ODBC.ini file in UNIX? in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328573#M9632</link>
    <description>&lt;P&gt;Thank you SASKiwi!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But the example in the reference using NOPROMPT still&amp;nbsp;has DSN which I think should be defined in the ODBC.ini file, right?&lt;/P&gt;&lt;P&gt;libname mydblib sqlsvr noprompt="uid=myusr1;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; pwd=mypwd1; &lt;FONT color="#0000ff"&gt;&lt;STRONG&gt;dsn=sqlservr&lt;/STRONG&gt;&lt;/FONT&gt;;" stringdates=yes;&lt;/P&gt;&lt;P&gt;So I think there is no way to avoid configuring ODBC.ini file, please correct me if I am wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jade&lt;/P&gt;</description>
    <pubDate>Mon, 30 Jan 2017 21:01:02 GMT</pubDate>
    <dc:creator>Jade_SAS</dc:creator>
    <dc:date>2017-01-30T21:01:02Z</dc:date>
    <item>
      <title>If access MS SQL data via SAS/Access to MS SQL , still need to edit ODBC.ini file in UNIX?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328489#M9625</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; We have SAS server under UNIX, if we access Microsoft SQL data via SAS/Access to Microsoft SQL data, is there a way&amp;nbsp;does not&amp;nbsp;need to edit ODBC.ini file?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I googled and found the following link, it seems we definitely still need to edit the ODBC.ini file even via SAS/Access to Microsoft SQL data (instead of the SAS/Access to ODBC)&lt;/P&gt;&lt;P&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/acreldb/63647/HTML/default/viewer.htm#a001405609.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/acreldb/63647/HTML/default/viewer.htm#a001405609.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please advise!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jade&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2017 16:14:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328489#M9625</guid>
      <dc:creator>Jade_SAS</dc:creator>
      <dc:date>2017-01-30T16:14:51Z</dc:date>
    </item>
    <item>
      <title>Re: If access MS SQL data via SAS/Access to MS SQL , still need to edit ODBC.ini file in UNIX?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328550#M9629</link>
      <description>&lt;P&gt;It is definitely possible for Windows SAS and this reference suggests it could be possible for Unix:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://communities.sas.com/t5/SAS-Communities-Library/How-to-configure-SAS-ACCESS-Interface-to-ODBC-on-UNIX-Platforms/ta-p/231900" target="_blank"&gt;https://communities.sas.com/t5/SAS-Communities-Library/How-to-configure-SAS-ACCESS-Interface-to-ODBC-on-UNIX-Platforms/ta-p/231900&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That is assuming SAS/ACCESS to SQL Server uses ODBC underneath.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You would usually use the NOPROMPT option say on a LIBNAME statement&amp;nbsp;to specify the connection string however this reference says it is not supported under Unix:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/acreldb/69580/HTML/default/viewer.htm#n0gz66qe8msnkyn1jgnhrr0l2k8y.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/acreldb/69580/HTML/default/viewer.htm#n0gz66qe8msnkyn1jgnhrr0l2k8y.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'd try this anyway just to confirm if it is correct or not. In my experience specifying database connections completely in a&amp;nbsp;LIBNAME or CONNECT&amp;nbsp;TO statement is way better than having to define DSNs elsewhere.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2017 19:30:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328550#M9629</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2017-01-30T19:30:21Z</dc:date>
    </item>
    <item>
      <title>Re: If access MS SQL data via SAS/Access to MS SQL , still need to edit ODBC.ini file in UNIX?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328573#M9632</link>
      <description>&lt;P&gt;Thank you SASKiwi!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But the example in the reference using NOPROMPT still&amp;nbsp;has DSN which I think should be defined in the ODBC.ini file, right?&lt;/P&gt;&lt;P&gt;libname mydblib sqlsvr noprompt="uid=myusr1;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; pwd=mypwd1; &lt;FONT color="#0000ff"&gt;&lt;STRONG&gt;dsn=sqlservr&lt;/STRONG&gt;&lt;/FONT&gt;;" stringdates=yes;&lt;/P&gt;&lt;P&gt;So I think there is no way to avoid configuring ODBC.ini file, please correct me if I am wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jade&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2017 21:01:02 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328573#M9632</guid>
      <dc:creator>Jade_SAS</dc:creator>
      <dc:date>2017-01-30T21:01:02Z</dc:date>
    </item>
    <item>
      <title>Re: If access MS SQL data via SAS/Access to MS SQL , still need to edit ODBC.ini file in UNIX?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328609#M9639</link>
      <description>&lt;P&gt;Here is a typical&amp;nbsp;connection string we use for SAS under Windows and it completely defines the connection to SQL Server:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;noprompt = "server=MyServerName;DRIVER=SQL Server;Trusted Connection=yes;"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We don't have Unix SAS so I can't try this for Unix. But if you removed Trusted Connection=yes and added uid= and password = you might get something close to what might work under Unix. I'm keen to know how you get on.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2017 22:57:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328609#M9639</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2017-01-30T22:57:06Z</dc:date>
    </item>
    <item>
      <title>Re: If access MS SQL data via SAS/Access to MS SQL , still need to edit ODBC.ini file in UNIX?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328806#M9654</link>
      <description>&lt;P&gt;Thanks SASKiwi!&lt;/P&gt;&lt;P&gt;So the server name here is the real server name, not the name that set up in the ODBC file?&lt;/P&gt;&lt;P&gt;noprompt = "server=&lt;FONT color="#ff0000"&gt;MyServerName&lt;/FONT&gt;;DRIVER=SQL Server;Trusted Connection=yes;"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have SAS ODBC to SQL data installed in UNIX, now&amp;nbsp;thinking add on SAS/Access to Micosoft SQL data to reduce the work load of admin ( if no need to edit the ODBC.ini file in UNIX, we have a lot servers and databases, really a lot to manage in the ODBC.ini file for admin)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jade&lt;/P&gt;</description>
      <pubDate>Tue, 31 Jan 2017 16:43:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328806#M9654</guid>
      <dc:creator>Jade_SAS</dc:creator>
      <dc:date>2017-01-31T16:43:37Z</dc:date>
    </item>
    <item>
      <title>Re: If access MS SQL data via SAS/Access to MS SQL , still need to edit ODBC.ini file in UNIX?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328856#M9657</link>
      <description>&lt;P&gt;Yes it is the "real" server name. If you use SQL Server Studio then it is the server name you enter to connect to your required databases.&lt;/P&gt;</description>
      <pubDate>Tue, 31 Jan 2017 19:53:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328856#M9657</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2017-01-31T19:53:05Z</dc:date>
    </item>
    <item>
      <title>Re: If access MS SQL data via SAS/Access to MS SQL , still need to edit ODBC.ini file in UNIX?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328871#M9658</link>
      <description>&lt;P&gt;Thank you, this is really helpful!&lt;/P&gt;&lt;P&gt;Jade&lt;/P&gt;</description>
      <pubDate>Tue, 31 Jan 2017 20:56:22 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/If-access-MS-SQL-data-via-SAS-Access-to-MS-SQL-still-need-to/m-p/328871#M9658</guid>
      <dc:creator>Jade_SAS</dc:creator>
      <dc:date>2017-01-31T20:56:22Z</dc:date>
    </item>
  </channel>
</rss>

