There is actually a bug in the server properties for SSAS in SSMS (at least as of SSMS 17.x). It probably applies to your case too.
The actual compatibility mode that is used by your model is set in the model itself.
The server has 2 properties:
DefaultCompatibilityMode
- probably used only when Create is executed (without the compatibility)
SupportCompatibilityModes
which is a list of supported levels.
Execute the following XMLA
window in SSMS (taken from social.msdn):
<Discover xmlns="urn:schemas-microsoft-com:xml-analysis">
<RequestType>DISCOVER_XML_METADATA</RequestType>
<Restrictions>
<RestrictionList>
<ObjectExpansion>ObjectProperties</ObjectExpansion>
</RestrictionList>
</Restrictions>
<Properties>
<PropertyList>
</PropertyList>
</Properties>
</Discover>
Search for Compatibility. You should be able to see for an SSAS 2017 server:
<ddl400:DefaultCompatibilityLevel>1200</ddl400:DefaultCompatibilityLevel>
<ddl600:SupportedCompatibilityLevels>1100,1103,1200,1400</ddl600:SupportedCompatibilityLevels>
The DefaultCompatibilityLevel
should match the requested compatibility level. In your case 1400. You should be able to confirm the mode that the model is running in by checking its properties in SSMS. You can, of course, change only to SupportedCompatibilityLevels
. Should your required compatibility level not be listed, you are out of luck.