<?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: SQL Server Driver (Kerberos authentication?) in Connectivity &amp; Data Prep</title>
    <link>https://community.qlik.com/t5/Connectivity-Data-Prep/SQL-Server-Driver-Kerberos-authentication/m-p/1674938#M4931</link>
    <description>&lt;P&gt;The problem may seem less to do with authentication but what method is used to connect to the SQL Server in order to satisfy the authentication method. The problem reported is likely to be related to what is documented under &lt;A title="Field taging for source data with unrecognized formatting has changed in February 2019" href="https://support.qlik.com/articles/000077161" target="_self"&gt;Field tagging for source data with unrecognized formatting has changed in February 2019&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 12 Feb 2020 16:13:07 GMT</pubDate>
    <dc:creator>Andre_Sostizzo</dc:creator>
    <dc:date>2020-02-12T16:13:07Z</dc:date>
    <item>
      <title>SQL Server Driver (Kerberos authentication?)</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/SQL-Server-Driver-Kerberos-authentication/m-p/1534550#M3557</link>
      <description>&lt;P&gt;I am using QS April 2018 and I am having issues connecting to a SQL Server using the SQL Server specific driver with pass through authentication (Active Directory). I can connect to the problem SQL Server using ODBC and OLE DB using AD however there is a bug which causes these drivers not to recognize the “&lt;STRONG&gt;Date”&lt;/STRONG&gt; datatype correctly (note: datatime datatypes work as expected). Unfortunately, OLE DB and ODBC drivers read the date fields as a string. My guess is that SQL Server need to use Kerberos authentication. When I run the command below I will get “KERBEROS” on the server that works and I will get “NTLM” on the one that doesn’t. &amp;nbsp;&lt;/P&gt;&lt;P&gt;select auth_scheme from sys.dm_exec_connections where session_id=@@spid&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.microsoft.com/en-us/help/909801/how-to-make-sure-that-you-are-using-kerberos-authentication-when-you-c" target="_blank"&gt;https://support.microsoft.com/en-us/help/909801/how-to-make-sure-that-you-are-using-kerberos-authentication-when-you-c&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;I don’t want to trial and error my way through this issue if I can avoid it. Any help you can provide would be greatly appreciated! Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 28 Dec 2021 20:09:25 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/SQL-Server-Driver-Kerberos-authentication/m-p/1534550#M3557</guid>
      <dc:creator>wdchristensen</dc:creator>
      <dc:date>2021-12-28T20:09:25Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Server Driver (Kerberos authentication?)</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/SQL-Server-Driver-Kerberos-authentication/m-p/1674938#M4931</link>
      <description>&lt;P&gt;The problem may seem less to do with authentication but what method is used to connect to the SQL Server in order to satisfy the authentication method. The problem reported is likely to be related to what is documented under &lt;A title="Field taging for source data with unrecognized formatting has changed in February 2019" href="https://support.qlik.com/articles/000077161" target="_self"&gt;Field tagging for source data with unrecognized formatting has changed in February 2019&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2020 16:13:07 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/SQL-Server-Driver-Kerberos-authentication/m-p/1674938#M4931</guid>
      <dc:creator>Andre_Sostizzo</dc:creator>
      <dc:date>2020-02-12T16:13:07Z</dc:date>
    </item>
  </channel>
</rss>

