<?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 Microsoft SQL Server 2017 compatibility? in Connectivity &amp; Data Prep</title>
    <link>https://community.qlik.com/t5/Connectivity-Data-Prep/Microsoft-SQL-Server-2017-compatibility/m-p/87655#M450</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our DBA is in the process of moving our databases over to a SQL Server 2017 server. He set them up in compatibility mode. However, while it appears like I can connect to the database, I have not been able to get it to load the data without errors. I have not changed any of the SQL in the load script, just the data connection which works against our databases sitting on SQL Server 2016. Has anyone else had this issue, or do you know if support for SQL Server 2017 will be coming soon? (Currently running QS Server April 2018)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 13 Jul 2018 21:43:32 GMT</pubDate>
    <dc:creator>chadwatson</dc:creator>
    <dc:date>2018-07-13T21:43:32Z</dc:date>
    <item>
      <title>Microsoft SQL Server 2017 compatibility?</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/Microsoft-SQL-Server-2017-compatibility/m-p/87655#M450</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our DBA is in the process of moving our databases over to a SQL Server 2017 server. He set them up in compatibility mode. However, while it appears like I can connect to the database, I have not been able to get it to load the data without errors. I have not changed any of the SQL in the load script, just the data connection which works against our databases sitting on SQL Server 2016. Has anyone else had this issue, or do you know if support for SQL Server 2017 will be coming soon? (Currently running QS Server April 2018)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Jul 2018 21:43:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/Microsoft-SQL-Server-2017-compatibility/m-p/87655#M450</guid>
      <dc:creator>chadwatson</dc:creator>
      <dc:date>2018-07-13T21:43:32Z</dc:date>
    </item>
    <item>
      <title>Re: Microsoft SQL Server 2017 compatibility?</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/Microsoft-SQL-Server-2017-compatibility/m-p/87656#M451</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After some research we found that our service account did not have rights to all of the databases that it needed rights to. Once we fixed that we had no issues connecting to SQL Server 2017.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2018 16:28:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/Microsoft-SQL-Server-2017-compatibility/m-p/87656#M451</guid>
      <dc:creator>chadwatson</dc:creator>
      <dc:date>2018-07-17T16:28:12Z</dc:date>
    </item>
  </channel>
</rss>

