<?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 ODBC DSN with Windows Authorization in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/ODBC-DSN-with-Windows-Authorization/m-p/1390813#M422883</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a Windows ODBC DSN on Qlikview server for SQL Server db, and it uses Windows authorization to connect to database. If a developer uses the following code in his script:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ODBC CONNECT TO [MySQLODBC];&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When his QVW runs automatically by a trigger, whose Windows authorization does it use?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 21 Sep 2017 15:52:13 GMT</pubDate>
    <dc:creator>Jeffrey_Li</dc:creator>
    <dc:date>2017-09-21T15:52:13Z</dc:date>
    <item>
      <title>ODBC DSN with Windows Authorization</title>
      <link>https://community.qlik.com/t5/QlikView/ODBC-DSN-with-Windows-Authorization/m-p/1390813#M422883</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a Windows ODBC DSN on Qlikview server for SQL Server db, and it uses Windows authorization to connect to database. If a developer uses the following code in his script:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ODBC CONNECT TO [MySQLODBC];&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When his QVW runs automatically by a trigger, whose Windows authorization does it use?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Sep 2017 15:52:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ODBC-DSN-with-Windows-Authorization/m-p/1390813#M422883</guid>
      <dc:creator>Jeffrey_Li</dc:creator>
      <dc:date>2017-09-21T15:52:13Z</dc:date>
    </item>
    <item>
      <title>Re: ODBC DSN with Windows Authorization</title>
      <link>https://community.qlik.com/t5/QlikView/ODBC-DSN-with-Windows-Authorization/m-p/1390814#M422884</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It tries to use the authorization of the Service Account that is running the QlikView services. If it really has an authorization to access your DBMS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If that is not going to work, you can try filling the Section Access fields with credentials that do have access to your SQL Server DB. But the best/simplest/easiest solution would be to give the service account Read access to your DB.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Sep 2017 16:07:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ODBC-DSN-with-Windows-Authorization/m-p/1390814#M422884</guid>
      <dc:creator>Peter_Cammaert</dc:creator>
      <dc:date>2017-09-21T16:07:53Z</dc:date>
    </item>
    <item>
      <title>Re: ODBC DSN with Windows Authorization</title>
      <link>https://community.qlik.com/t5/QlikView/ODBC-DSN-with-Windows-Authorization/m-p/1390815#M422885</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Peter,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Sep 2017 18:17:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ODBC-DSN-with-Windows-Authorization/m-p/1390815#M422885</guid>
      <dc:creator>Jeffrey_Li</dc:creator>
      <dc:date>2017-09-21T18:17:44Z</dc:date>
    </item>
  </channel>
</rss>

