<?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: how to create a libname odbc with windows authentication in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-create-a-libname-odbc-with-windows-authentication/m-p/14160#M2937</link>
    <description>Hi, there is also a nice solution using OLEDB access:&lt;BR /&gt;
&lt;BR /&gt;
LIBNAME name OLEDB  INIT_STRING="Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=True;Data Source=***;Initial Catalog=***"  PROMPT=NO  PROVIDER=SQLOLEDB.1  DATASOURCE=***  SCHEMA=*** ;&lt;BR /&gt;
&lt;BR /&gt;
No need for registering system dependnt DSN.</description>
    <pubDate>Thu, 19 Nov 2009 10:16:34 GMT</pubDate>
    <dc:creator>deleted_user</dc:creator>
    <dc:date>2009-11-19T10:16:34Z</dc:date>
    <item>
      <title>how to create a libname odbc with windows authentication</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-create-a-libname-odbc-with-windows-authentication/m-p/14157#M2934</link>
      <description>I would like to create a libname to a SQL db with windows authentication, like this one:&lt;BR /&gt;
&lt;BR /&gt;
libname lib_name odbc dsn=dsn_name user=xxxx password=xxxx schema="";&lt;BR /&gt;
&lt;BR /&gt;
but instead of using user and password, I'd like to use my windows authentication. &lt;BR /&gt;
&lt;BR /&gt;
The goal of my procedure is: using a procedure without using a user and password pre-defined. &lt;BR /&gt;
&lt;BR /&gt;
any help?&lt;BR /&gt;
&lt;BR /&gt;
Tks</description>
      <pubDate>Mon, 09 Nov 2009 21:37:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-create-a-libname-odbc-with-windows-authentication/m-p/14157#M2934</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-11-09T21:37:34Z</dc:date>
    </item>
    <item>
      <title>Re: how to create a libname odbc with windows authentication</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-create-a-libname-odbc-with-windows-authentication/m-p/14158#M2935</link>
      <description>What you are talking about is called a "trust relationship" between the SQL database and the other OS uses.  Microsoft SQL/Server supports it, I'm not sure about other products.  That has to be set up by the SQL database administrators.  Many DBAs consider it a security risk and are unwilling to support it, so "good luck."</description>
      <pubDate>Tue, 10 Nov 2009 16:24:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-create-a-libname-odbc-with-windows-authentication/m-p/14158#M2935</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2009-11-10T16:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: how to create a libname odbc with windows authentication</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-create-a-libname-odbc-with-windows-authentication/m-p/14159#M2936</link>
      <description>tks for the help, but I've fixed it.&lt;BR /&gt;
&lt;BR /&gt;
I've created a DSN with "log in with windows NT authentication" and in my libname I've put something like this:&lt;BR /&gt;
&lt;BR /&gt;
libname mylib odbc dsn='dsn_name' schema=dbo;&lt;BR /&gt;
&lt;BR /&gt;
that means, I didnot need to put user and pass if the DSN has that configuration.&lt;BR /&gt;
&lt;BR /&gt;
Tks anyway</description>
      <pubDate>Tue, 10 Nov 2009 19:59:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-create-a-libname-odbc-with-windows-authentication/m-p/14159#M2936</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-11-10T19:59:31Z</dc:date>
    </item>
    <item>
      <title>Re: how to create a libname odbc with windows authentication</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-create-a-libname-odbc-with-windows-authentication/m-p/14160#M2937</link>
      <description>Hi, there is also a nice solution using OLEDB access:&lt;BR /&gt;
&lt;BR /&gt;
LIBNAME name OLEDB  INIT_STRING="Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=True;Data Source=***;Initial Catalog=***"  PROMPT=NO  PROVIDER=SQLOLEDB.1  DATASOURCE=***  SCHEMA=*** ;&lt;BR /&gt;
&lt;BR /&gt;
No need for registering system dependnt DSN.</description>
      <pubDate>Thu, 19 Nov 2009 10:16:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-create-a-libname-odbc-with-windows-authentication/m-p/14160#M2937</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-11-19T10:16:34Z</dc:date>
    </item>
  </channel>
</rss>

