locked
SQL Server 2017 SSAS supported compatibility level RRS feed

  • Question

  • I have installed the developer edition of SQL Server 2017 and also applied SQLServer2017-KB4038634-x64.exe on top of it.

    When I connect to SSAS in SSMS 2017 (v17.3) I am informed that the version of SSAS = 14.0.1.439.

    The properties for this server shows a.o.: supported compatibility level = 1200.

    The documentation on SQL Server 2017 tells me that the  supported compatibility level should be 1400.

    Am I somehow running an old version of SQL Server 2017 ?

    ( The database engine is at version 14.0.3006.16 )

    Sunday, November 26, 2017 5:14 AM

Answers

All replies

    • Marked as answer by Adri Vinke Monday, November 27, 2017 1:42 PM
    Sunday, November 26, 2017 4:52 PM
  • I'm pretty sure that's a bug. It looks to me like someone has mapped the default compatibility mode to the "supported" label in the UI. If you run a DISCOVER_XML_METADATA request against the server like the following one:

       

    <Discover xmlns="urn:schemas-microsoft-com:xml-analysis">
    <RequestType>DISCOVER_XML_METADATA</RequestType>
        <Restrictions>
    <RestrictionList>
    </RestrictionList>
    </Restrictions>
        <Properties>
    <PropertyList>
    </PropertyList>
    </Properties>
    </Discover>

    You will find the following as part of the results showing that 1200 is the default, but the supported list is 1100,1103,1200,1400

    <Version>14.0.1.439</Version>
    <Edition>Developer64</Edition>
    <EditionID>2176971986</EditionID>
    <ddl300:ServerMode>Tabular</ddl300:ServerMode>
    <ddl400:ServerLocation>OnPremise</ddl400:ServerLocation>
    <ddl400:DefaultCompatibilityLevel>1200</ddl400:DefaultCompatibilityLevel>
    <ddl600:SupportedCompatibilityLevels>1100,1103,1200,1400</ddl600:SupportedCompatibilityLevels>
    <ProductLevel>RTM</ProductLevel>
    <ProductName>Microsoft SQL Server Analysis Services</ProductName>

    I've logged a connect issue for this bug here https://connect.microsoft.com/SQLServer/feedback/details/3144432 if you want to vote for it to be fixed


    http://darren.gosbell.com - please mark correct answers


    Sunday, November 26, 2017 8:27 PM
  • Hi Adri Vinke,

    Thanks for your question.

    Since Darren has submitted this issue to the Microsoft Connect. Please vote for it and trace this issue in the Microsoft Connect site.This connect site will serve as a connecting point between you and Microsoft, and ultimately the large community for you and Microsoft to interact with. Your feedback enables Microsoft to offer the best software and deliver superior services, meanwhile you can learn more about and contribute to the exciting projects on Microsoft Connect.


    Best Regards
    Willson Yuan
    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com


    Monday, November 27, 2017 5:55 AM
  • I am on the latest SQL Server 2017 Build 14.0.3015.40 (CU3), SSAS 14.0.202.1, and SSMS 17.4, and I still have this issue.  I am trying to have supported compatibility level 1400 on AS server as noted in Microsoft Docs, but it displays as 1200. 
    Friday, January 5, 2018 2:47 AM
  • I am on the latest SQL Server 2017 Build 14.0.3015.40 (CU3), SSAS 14.0.202.1, and SSMS 17.4, and I still have this issue.  I am trying to have supported compatibility level 1400 on AS server as noted in Microsoft Docs, but it displays as 1200. 
    That probably just means that the fix for SSMS did not make it in to the 17.4 release. If you run the discover command I posted a few replies ago it will show you the correct information.

    http://darren.gosbell.com - please mark correct answers

    Friday, January 5, 2018 1:07 PM
  • The Supported Compatibility Level for SSAS 2017 with Cumulative Update 6 is still showing as 1200 in SSMS.

    SSAS version is 14.0.204.1. 

    Microsoft SQL Server Management Studio version   14.0.17254.0

    The Discover command that Darren provided earlier in this thread does show the correct Compatibility level. 

    Thanks Darren.

    <Discover xmlns="urn:schemas-microsoft-com:xml-analysis">
    <RequestType>DISCOVER_XML_METADATA</RequestType>
        <Restrictions>
    <RestrictionList>
    </RestrictionList>
    </Restrictions>
        <Properties>
    <PropertyList>
    </PropertyList>
    </Properties>
    </Discover>

    Friday, May 18, 2018 1:43 PM
  • Hi guys, 

    This issue still persists in SSMS 17.9, and running the XMLA lists the correct versions. 

    However, my SSDT (VS Data Tools 2015) does not list the 1400 compatibility. I've got SQL Server developer edition, with SSAS tabular installed 14.0.230.1. 

    And, I am trying to work with WWImporters Tabular model from MS.

    Update

    Microsoft SQL Server 2017 Setup Discovery Report

    Product Instance Instance ID Feature Language Edition Version Clustered Configured
    Microsoft SQL Server 2017 MSSQLSERVER MSSQL14.MSSQLSERVER Database Engine Services 1033 Developer Edition 14.0.3045.24 No Yes
    Microsoft SQL Server 2017 MSSQLSERVER MSSQL14.MSSQLSERVER Machine Learning Services (In-Database) 1033 Developer Edition 14.0.3045.24 No Yes
    Microsoft SQL Server 2017 MSSQLSERVER MSSQL14.MSSQLSERVER AdvancedAnalytics\sql_inst_mr 1033 Developer Edition 14.0.3045.24 No Yes
    Microsoft SQL Server 2017 MSSQLSERVER MSSQL14.MSSQLSERVER AdvancedAnalytics\sql_inst_mpy 1033 Developer Edition 14.0.3045.24 No Yes
    Microsoft SQL Server 2017 MSSQLSERVER MSAS14.MSSQLSERVER Analysis Services 1033 Developer Edition 14.0.3045.24 No Yes
    Microsoft SQL Server 2017 TABULAR17 MSAS14.TABULAR17 Analysis Services 1033 Developer Edition 14.0.3045.24 No Yes
    Microsoft SQL Server 2017 Client Tools Connectivity 1033 14.0.1000.169 No Yes
    Microsoft SQL Server 2017 Client Tools Backwards Compatibility 1033 14.0.1000.169 No Yes
    Microsoft SQL Server 2017 Client Tools SDK 1033 14.0.1000.169 No Yes
    Microsoft SQL Server 2017 Integration Services 1033 Developer Edition 14.0.3045.24 No Yes
    Microsoft SQL Server 2017 Scale Out Master 1033 Developer Edition 14.0.1000.169 No Yes
    Microsoft SQL Server 2017 Scale Out Worker 1033 Developer Edition 14.0.3045.24 No Yes


    Thanks

    kaz


    • Edited by Kazim Rajani Wednesday, October 31, 2018 8:40 AM
    Wednesday, October 31, 2018 8:38 AM
  • Darren, 

    We are having the same issues. Since Microsoft Connect was discontinued and we cannot see the status of your ticket. Any idea, how this got solved ? 

     Thanks


    Wednesday, October 31, 2018 8:00 PM
  • @Nick - this still does not look like it's been solved.

    The connect item appears to have been moved to this user voice item https://feedback.azure.com/forums/908035-sql-server/suggestions/32896885-ssas-supported-compatibility-level-is-actually-sho

    If you run the XMLA query I posted above you can see the correct values from the server. Or you could run the following DMV queries

    select * from $SYSTEM.DISCOVER_PROPERTIES
    WHERE PropertyName = 'DefaultCompatibilityLevel'

    select * from $SYSTEM.DISCOVER_PROPERTIES
    WHERE PropertyName = 'SupportedCompatibilityLevels'


    http://darren.gosbell.com - please mark correct answers

    Wednesday, October 31, 2018 9:55 PM