6 Appendix A: Product Behavior

  • Artículo

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Microsoft Office 2010 system

  • Microsoft Office 2013 system

  • Microsoft Office 2016

  • Microsoft Office 2019

  • Microsoft Office 2021

  • Microsoft Office LTSC 2024

  • Microsoft SQL Server 2005

  • Microsoft SQL Server 2008

  • Microsoft SQL Server 2008 R2

  • Microsoft SQL Server 2012

  • Microsoft SQL Server 2014

  • Microsoft SQL Server 2016

  • Microsoft SQL Server 2017

  • Microsoft SQL Server 2019

  • Microsoft SQL Server 2022

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 2.1.1: Microsoft SQL Server Analysis Services does break down DIME messages into multiple records.

<2> Section 2.1.1: Analysis Services sets the RESERVED field in the DIME record to 0.

<3> Section 2.1.1: By default, Analysis Services uses the content type application/sx+xpress. However, it can be configured to use the other content types (text/xml, application/sx, or application/xml+xpress).

<4> Section 2.1.2: With the exception of Microsoft SQL Server 2005 Analysis Services and Microsoft SQL Server 2008 Analysis Services, Microsoft SQL Server supports HTTP connectivity by using the following format, where DataSource points to an Analysis Services database on PowerPivot for SharePoint along with the corresponding locale ID. The client application can optionally include an initial XMLA message as the body of the POST.

 POST http://mysharepointsite/_vti_bin/PowerPivot/Redirector.svc/?DataSource=/PowerPivot%20Gallery/MyPPWorkbook.xlsx&LocaleID=1033 HTTP/1.1

The client receives the database ID from Analysis Services. The database ID needs to be included in subsequent POSTs. The following is an example of the post with the database ID.

 POST http:// mysharepointsite/_vti_bin/PowerPivot/Redirector.svc/?DatabaseId=26551F5D-C357-48AD-B3D0-FABBFB4E795C HTTP/1.1

<5> Section 2.1.2: X-AS-ActivityID is used only when an Analysis Services client is connecting to Office 365. X-AS-ActivityID is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to Microsoft SQL Server 2012 Service Pack 1 (SP1).

<6> Section 2.1.2: X-AS-GetSessionToken is used only when an Analysis Services client is connecting to Office 365. X-AS-GetSessionToken is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<7> Section 2.1.2: X-AS-RequestID is used only when an Analysis Services client is connecting to Office 365. X-AS-RequestID is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<8> Section 2.1.2: X-AS-SessionID is used only when an Analysis Services client is connecting to Office 365. X-AS-SessionID is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<9> Section 2.1.2: Content-Encoding is used only when an Analysis Services client is connecting to Office 365. Content-Encoding is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<10> Section 2.1.2: Authorization is used only when an Analysis Services client is connecting to Office 365. Authorization is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<11> Section 2.2.1: The eng100 namespace is not supported by SQL Server 2005.

<12> Section 2.2.1: The eng100_100 namespace is not supported by SQL Server 2005.

<13> Section 2.2.1: The eng200 namespace is not supported by SQL Server 2005 and SQL Server 2008.

<14> Section 2.2.1: The eng200_200 namespace is not supported by SQL Server 2005 and SQL Server 2008.

<15> Section 2.2.1: The eng300 namespace is not supported by SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2.

<16> Section 2.2.1: The eng300_300 namespace is not supported by SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2.

<17> Section 2.2.1: The eng400 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<18> Section 2.2.1: The eng400_400 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<19> Section 2.2.1: The eng500 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014.

<20> Section 2.2.1: The eng500_500 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014.

<21> Section 2.2.1: The eng600 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, and SQL Server 2016.

<22> Section 2.2.1: The eng600_600 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, and SQL Server 2016.

<23> Section 2.2.1: The eng800 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017.

<24> Section 2.2.1: The eng800_800 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017.

<25> Section 2.2.1:  The eng900 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<26> Section 2.2.1:  The eng900_900 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<27> Section 2.2.1:  The eng910 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<28> Section 2.2.1:  The eng910_910 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<29> Section 2.2.1:  The eng920 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<30> Section 2.2.1:  The eng920_920 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<31> Section 2.2.1:  The eng921 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<32> Section 2.2.1:  The eng921_921 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<33> Section 2.2.1:  The eng922 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<34> Section 2.2.1:  The eng922_922 namespace is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<35> Section 2.2.4.1.1.2.1.1: Analysis Services supports only the Tuples set type. It does not support Members, CrossProduct, and Union set types.

<36> Section 2.2.4.1.1.2.1.1.5: Analysis Services does not support the CrossProduct element or the SetListType complex type.

<37> Section 2.2.4.1.1.2.1.2: The NormType model group is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1. The NormType model group is supported only when Analysis Services is running in Tabular mode. However, Analysis Services always returns the SetType model group, even when the MDX query statement is sent with the DbpropMsmdOptimizeResponse property set to "7".

<38> Section 2.2.4.1.1.2.1.2.1: The MetadatasType type is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1. The MetadatasType type is supported only when Analysis Services is running in Tabular mode.

<39> Section 2.2.4.1.1.2.1.2.2: The MetadataType type is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1. The MetadataType type is supported only when Analysis Services is running in Tabular mode.

<40> Section 2.2.4.1.1.2.1.2.2: The MemberFormatString attribute is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<41> Section 2.2.4.1.1.2.1.2.3: The TuplesNormType type is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1. The TuplesNormType type is supported only when Analysis Services is running in Tabular mode.

<42> Section 2.2.4.1.1.2.1.2.4: The KeysNormType type is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1. The KeysNormType type is supported only when Analysis Services is running in Tabular mode.

<43> Section 2.2.4.1.1.2.1.2.5: The KeyNormType type is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1. The KeyNormType type is supported only when Analysis Services is running in Tabular mode.

<44> Section 2.2.4.1.1.2.1.2.6: The MeasureFormatStringsNormType attribute is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1. The MeasureFormatStringsNormType type is supported only when Analysis Services is running in Tabular mode.

<45> Section 2.2.4.1.1.2.1.2.7: The MeasureFormatStringNormType attribute is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1. The MeasureFormatStringNormType type is supported only when Analysis Services is running in Tabular mode.

<46> Section 2.2.4.2.1.1: Analysis Services has additional rules that apply to names and IDs:

  • The maximum number of characters is 100.

  • There are no special requirements for the first character of an identifier. Same rules as for other valid characters apply.

  • The following reserved names are not to be used:

    • AUX

    • CLOCK$

    • COM1 through COM9 (COM1, COM2, COM3, and so on)

    • CON

    • LPT1 through LPT9 (LPT1, LPT2, LPT3, and so on)

    • NUL

    • PRN

  • NULL is not used as a character in any string within the XML.

The following table lists invalid characters for each type of object:

Object

Invalid Characters

Server

The name has to follow the rules that are supported by the Windows operating system for computer names. (IP addresses are not valid.)

Data Source

: / \ * | ? " () [] {} <>

Level and Attribute

. , ; ' ` : / \ * | ? " & % $ ! + = [] {} < >

Dimension and Hierarchy

.,, ; ' ` : / \ * | ? " & % $ ! + = () [] {} <,>

All other objects

. , ; ' ` : / \ * | ? " & % $ ! + = () [] {} < >

A DataSource reference that consists of a single period means the current database of the current analysis server. For example, DataSourceID./DataSourceID points to the current database of the current analysis server instance.

<47> Section 2.2.4.2.1.1: When the deployment mode of a server that is running Analysis Services is set to 1 or 2 and the database compatibility level is set to 1103 or higher, the name validation is relaxed. That is, for the DimensionAttribute, Hierarchy, Level, Measure (which is a DAX measure that is declared in MdxScript), and KPI objects, the characters , ; ' ` : / \ * | ? " & % $ ! + = [ ] { } < > ( ) are valid and the reserved names AUX and COM1 through COM9 (COM1, COM2, COM3, and so on) can be used. This behavior is not supported in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<48> Section 2.2.4.2.1.2: In Analysis Services, the following cases are handled by the server when they are encountered and they are the values of string elements:

  • Leading and trailing white space is trimmed.

  • Internal white space is preserved.

  • The following characters are stripped out:

    • Values below 0x20 (except 0x09, 0x0A, and 0x0D).

    • Values above and including 0x110000.

<49> Section 2.2.4.2.1.4: Analysis Services does not enforce that elements be in a stated sequence.

<50> Section 2.2.4.2.2.2: In Analysis Services, the ID for the edition is obtained from sqlboot.dll Zero for local cubes.

<51> Section 2.2.4.2.2.2: In Analysis Services, the product version is obtained from sqlver.h.

<52> Section 2.2.4.2.2.2.1: Server properties that are supported by Analysis Services are described in the following table.

Note Some of the properties in this table are returned by DISCOVER_XML_METADATA. If a property is not returned by DISCOVER_XML_METADATA, it can be found in the configuration file on a server that is running Analysis Services. This file is named msmdsrv.ini and can be found in the installation folder tree after the product is installed.

Property

Default value

Description

AdminTimeout

0

A signed 32-bit integer property that defines the administrator timeout in seconds.

AllowedBrowsingFolders

"\data"

A string property that defines the names of the folders where logs, backups, and other objects are allowed to be created on the server, in the form of a comma-separated list.

BackupDir

Empty

A string property that identifies the name of the directory where backup files are created by default, in the event a path is not specified as part of the Backup command.

CollationName

Empty

A string property that identifies the server collation. For more information, see [MSDN-LCAS].

CommitTimeout

0

A signed 32-bit integer property that defines the number of milliseconds before pending commit operations time out. Zero indicates that the server will not time out commit operations.

CoordinatorBuildMaxThreads

4

A signed 32-bit integer property that defines the maximum number of threads allocated to building partition indexes. Increase this value in order to speed-up partition indexing, at the cost of memory usage.

CoordinatorCancelCount

1000

A signed 32-bit integer property that defines how frequently the server is to check whether a Cancel event occurred (based on internal iteration count). Decrease this number in order to check for Cancel more frequently, at the expense of general performance.

CoordinatorExecutionMode

-4

A signed 32-bit integer property that defines the maximum number of parallel operations the server will attempt, including processing and querying operations. Zero (0) indicates that the server will decide, based on an internal algorithm. A positive number indicates the maximum number of operations in total. A negative number, with the sign reversed, indicates the maximum number of operations per processor.

DataDir

"\data"

A string property that identifies the name of the directory where data is stored.

ExternalCommandTimeout

3600

A signed 32-bit integer property that defines the timeout, in seconds, for commands issued to external servers, including relational data sources and external servers that are running Analysis Services.

ExternalConnectionTimeout

60

A signed 32-bit integer property that defines the timeout, in seconds, for creating connections to external servers, including relational data sources and external servers that are running Analysis Services.

ForceCommitTimeout

30000

A signed 32-bit integer property that defines the timeout, in milliseconds, before a commit is to cancel other commands that preceded the current command, including queries in process.

IdleConnectionTimeout

0

A signed 32-bit integer property that defines the idle connection timeout, in seconds. The value zero (0) indicates that idle connections will not be timed out.

IdleOrphanSessionTimeout

120

A signed 32-bit integer property that defines how long orphaned sessions will be retained in server memory in seconds.

InstanceVisible

true

When true, indicates that the server instance is visible to discover instance requests; otherwise, false.

Language

0

A string property that defines the language, including error messages and number formatting. This property overrides the CollationName property. Blank indicates that the CollationName property defines the language.

LogDir

Empty

A string property that identifies the name of the directory that contains server logs. This property only applies when disk files are used for logging, as opposed to database tables (the default behavior).

MaxIdleSessionTimeout

0

A signed 32-bit integer property that defines the maximum idle session timeout, in seconds.

MinIdleSessionTimeout

2700

A signed 32-bit integer property that defines the minimum time, in seconds, that idle sessions will timeout. After this time expires, the server is permitted to end the idle session, but will only do so as memory is needed.

Port

0

A signed 32-bit integer property that defines the port number on which server will listen for client connections. If not set, server dynamically finds first unused port. Zero (0) means that port 2383 will be used.

ServerTimeout

3600

A signed 32-bit integer property that defines the timeout in seconds for queries.

TempDir

Empty

A string property that identifies the name of the directory for defining temporary files used for processing, restoring, and other operations. If not specified, the default is the Data directory.

DataMining\Algorithms\Microsoft_Association_Rules\Enabled

true

When true, indicates that the Microsoft_Association_Rules algorithm is enabled; otherwise, false.

DataMining\Algorithms\Microsoft_Clustering\Enabled

true

When true, indicates that the Microsoft_Clustering algorithm is enabled; otherwise, false.

DataMining\Algorithms\Microsoft_Decision_Trees\Enabled

true

When true, indicates that the Microsoft_DecisionTrees algorithm is enabled; otherwise, false.

DataMining\Algorithms\Microsoft_Linear_Regression\Enabled

true

When true, indicates that the Microsoft_Linear_Regression algorithm is enabled; otherwise, false.

DataMining\Algorithms\Microsoft_Logistic_Regression\Enabled

true

When true, indicates that the Microsoft_Logistic_Regression algorithm is enabled; otherwise, false.

DataMining\Algorithms\Microsoft_Naive_Bayes\Enabled

true

When true, indicates that the Microsoft_ Naive_Bayes algorithm is enabled; otherwise, false.

DataMining\Algorithms\Microsoft_Neural_Network\Enabled

true

When true, indicates that the Microsoft_Neural_Network algorithm is enabled; otherwise, false.

DataMining\Algorithms\Microsoft_Sequence_Clustering\Enabled

true

When true, indicates that the Microsoft_Sequence_Clustering algorithm is enabled; otherwise, false.

DataMining\Algorithms\Microsoft_Time_Series\Enabled

true

When true, indicates that the Microsoft_Time_Series algorithm is enabled; otherwise, false.

DataMining\AllowAdHocOpenRowsetQueries

false

When true, indicates that ad hoc open rowset queries are allowed; otherwise, false.

DataMining\AllowedProvidersInOpenRowset

Empty

A string property that identifies which providers are allowed in an open rowset, consisting of a comma/semi-colon separated list of provider ProgIDs, or else [All].

DataMining\AllowSessionMiningModels

false

When true, indicates that session mining models can be created; otherwise, false.

DataMining\MaxConcurrentPredictionQueries

0

A signed 32-bit integer property that defines the maximum number of concurrent prediction queries.

DSO\LocksDirectory

Empty

LocksDirectory is a folder where Decision Support Objects (DSO) keeps locking information. Locking information is created and deleted in this folder without any user intervention. Complete access to create, modify, and delete files is required in this folder for all DSO applications. LocksDirectory contains the path of the folder.

DSO\RemoteLocksDirectory

Empty

RemoteLocksDirectory contains the path of a shared folder where locks are kept for DSO applications.

DSO\RemoteRepositoryConnectionString

Empty

RemoteRepositoryConnectionString is a standard OLEDB SQL Server connection string that points to the SQL Server Analysis Services repository. If repository is a Microsoft Access database (an .mdb file), then the path of the file is a path of a shared folder. RemoteRepositoryConnectionString is used by DSO when the repository is located on a remote server. DSO checks the name of the server. If the name of the server is localhost or it is the name of the computer, then DSO uses RepositoryConnectionString, otherwise DSO uses RemoteRepositoryConnectionString.

DSO\RepositoryConnectionString

Empty

RepositoryConnectionString is a standard OLEDB connection string that points to the SQL Server repository. If the repository is a Microsoft Access database (an .mdb file), then the path of the file is a local path. RepositoryConnectionString is used by DSO when repository is locally available on the server. DSO checks the name of the server. If the name of the server is localhost or it is the name of the computer, then DSO uses RepositoryConnectionString, otherwise DSO uses RemoteRepositoryConnectionString.

Feature\ComUdfEnabled

false

When true, indicates that user-defined functions defined as com objects are enabled; otherwise, false.

Feature\LinkFromOtherInstanceEnabled

false

When true, indicates that objects can be linked to from other server instances; otherwise, false.

Feature\LinkInsideInstanceEnabled

true

When true, indicates that a linked object can be created inside the same server instance; otherwise, false.

Feature\LinkToOtherInstanceEnabled

false

When true, indicates that objects on remote servers can be linked to; otherwise, false.

Log\ErrorLog\ErrorLogFileName

Empty

A property used as a default during processing operation performed by the server.

Log\ErrorLog\ErrorLogFileSize

4

A property used as a default during processing operation performed by the server.

Log\ErrorLog\KeyErrorAction

0

A property used as a default during processing operation performed by the server.

Log\ErrorLog\KeyErrorLimit

0

A property used as a default during processing operation performed by the server.

Log\ErrorLog\KeyErrorLimitAction

0

A property used as a default during processing operation performed by the server.

Log\ErrorLog\KeyErrorLogFile

Empty

A property used as a default during processing operation performed by the server.

Log\ErrorLog\LogErrorTypes\KeyDuplicate

0

A property used as a default during processing operation performed by the server.

Log\ErrorLog\LogErrorTypes\KeyNotFound

1

A property used as a default during processing operation performed by the server.

Log\ErrorLog\LogErrorTypes\NullKeyConvertedToUnknown

0

A property used as a default during processing operation performed by the server.

Log\ErrorLog\LogErrorTypes\NullKeyNotAllowed

1

A property used as a default during processing operation performed by the server.

Log\File

"msmdsrv.log"

A string property that identifies the name of the server log file. This property only applies when a disk file is used for logging, as opposed to a database table (the default behavior).

Log\FlightRecorder\Enabled

true

When true, indicates that the flight recorder feature is enabled; otherwise, false.

Log\FlightRecorder\FileSizeMB

10

A signed 32-bit integer property that defines the size of the flight recorder disk file, in megabytes.

Log\FlightRecorder\LogDurationSec

3600

A signed 32-bit integer property that defines the frequency that the flight recorder is rolled over, in seconds.

Log\FlightRecorder\SnapshotDefinitionFile

Empty

A string property that defines the name of the snapshot definition file, containing discover commands that are issued to the server when a snapshot is taken. Blank signifies file name FlightRecorderSnapshotDef.xml.

Log\FlightRecorder\SnapshotFrequencySec

120

A signed 32-bit integer property that defines the snapshot frequency, in seconds.

Log\FlightRecorder\TraceDefinitionFile

Empty

A string property that specifies the name of the flight recorder trace definition file. Blank indicates FlightRecorderTraceDef.xml.

Log\MessageLogs

"File;Console;System"

It is advised that this advanced property not be changed, except under the guidance of Microsoft support.

Log\QueryLog\CreateQueryLogTable

false

When true, specifies to create the query log table; otherwise, false.

Log\QueryLog\QueryLogConnectionString

Empty

A string property that specifies the connection to the query log database.

Log\QueryLog\QueryLogFileName

Empty

A string property that specifies the name of the query log file. This property only applies when a disk file is used for logging, as opposed to a database table (the default behavior).

Log\QueryLog\QueryLogSampling

10

A signed 32-bit integer property that specifies the query log sampling rate. 10, for example, means that 1 out of every 10 server queries is logged.

Log\QueryLog\QueryLogTableName

"OlapQueryLog"

A string property that specifies the name of the query log table.

Log\Trace\TraceReportFQDN

0

It is advised that this advanced property not be changed, except under the guidance of Microsoft support.

Memory\HardMemoryLimit

0

The target maximum memory use for the server. If memory use exceeds this value, the server will free all shrinkable memory, and if memory use still exceeds the limit after freeing all shrinkable memory, the server will kill all running commands. Default is (TotalMemoryLimit + min (system physical memory, system total available virtual memory))/2.

Memory\HeapTypeForObjects

0

In Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the default value is 1.

It is advised that this advanced property not be changed, except under the guidance of Microsoft support.

Memory\LowMemoryLimit

65

A signed 64-bit double-precision floating-point number property that defines the point at which the server is low on memory, expressed as percentage of total physical memory. When this threshold is reached, the server aggressively looks for opportunities to free up memory.

Memory\MemoryHeapType

-1

In Analysis Services in SQL Server 2012 SP1, SQL Server 2012 SP2, SQL Server 2014, and SQL Server 2016 prior to SQL Server 2016 SP1, the default value is 2.

In Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the default value is 1.

It is advised that this advanced property not be changed, except under the guidance of Microsoft support.

Memory\QueryMemoryLimit

0

An advanced property that controls how much memory can be used during a query, expressed as a percentage of available memory. An estimate of the memory used by the query is computed. If the estimate exceeds the stated limit, an error can be raised. The default value of 0 means that there is no limit.

Memory\TotalMemoryLimit

80

A property that defines the maximum physical memory the server will use, expressed as percentage of total physical memory.

Network\Listener\IPV4Support

2

In Analysis Services in SQL Server 2005 and SQL Server 2008, the default value is 1.

A signed 32-bit integer property that defines support for IPv4 protocol. This property can have one of the following values:

  • 0 – IPv4 disabled

  • 1 – IPv4 required

  • 2 – IPv4 optional

Network\Listener\IPV6Support

2

A signed 32-bit integer property that defines support for IPv6 protocol. This property can have one of the following values:

  • 0 – IPv6 disabled

  • 1 – IPv6 required

  • 2 – IPv6 optional

Network\Listener\MaxAllowedRequestSize

0

It is advised that this advanced property not be changed, except under the guidance of Microsoft support.

Network\ListenOnlyOnLocalConnections

false

When true, specifies to listen only on local connections, for example localhost; otherwise, false.

Network\Requests\EnableBinaryXML

false

When true, specifies that the server will recognize requests binary xml format; otherwise, false.

Network\Requests\EnableCompression

false

When true, specifies that compression is enabled for requests; otherwise, false.

Network\Responses\EnableBinaryXML

true

When true, specifies that the server is enabled for binary xml responses; otherwise, false.

Network\Responses\EnableCompression

true

When true, specifies that compression is enabled for responses to client requests; otherwise, false.

OLAP\LazyProcessing\Enabled

true

When true, specifies that lazy aggregation processing is enabled; otherwise, false.

OLAP\LazyProcessing\MaxCPUUsage

0.5

A signed 64-bit double-precision floating-point number property that defines maximum CPU usage for lazy processing, expressed as a percentage. The server monitors average CPU use based on snapshots. It is normal behavior for the CPU to spike above this threshold.

OLAP\LazyProcessing\MaxObjectsInParallel

2

A signed 32-bit integer property that specifies the maximum number of partitions that can be lazily processed in parallel.

OLAP\LazyProcessing\MaxRetries

3

A signed 32-bit integer property that defines the number of retries in the event that lazy processing fails before an error is raised.

OLAP\LazyProcessing\SleepIntervalSecs

5

A signed 32-bit integer property that defines the interval, in seconds, that the server checks whether there are lazy processing jobs pending.

OLAP\Process\AggregationMemoryLimitMax

80

A signed 64-bit double-precision floating-point number property that defines the maximum amount of memory that can be devoted to aggregation processing, expressed as a percentage of physical memory.

OLAP\Process\AggregationMemoryLimitMin

10

A signed 64-bit double-precision floating-point number property that defines the minimum amount of memory that can be devoted to aggregation processing, expressed as a percentage of physical memory. A larger value can speed up aggregation processing at the cost of memory usage.

OLAP\Process\BufferMemoryLimit

60

A signed 64-bit double-precision floating-point number property that defines the processing buffer memory limit, expressed as a percent of physical memory.

OLAP\Process\CheckDistinctRecordSortOrder

1

An int property that defines if the sort order for the results of a distinct count query are meaningful when processing partitions. True indicates that the sort order is not meaningful and has to be checked by the server. When processing partitions with distinct count measure, query sent to SQL with order-by. Set to false to speed up processing.

OLAP\Process\DatabaseConnectionPoolConnectTimeout

60

A signed 32-bit integer property that specifies timeout when opening a new connection in seconds.

OLAP\Process\DatabaseConnectionPoolGeneralTimeout

60

A signed 32-bit integer property that specifies database connection timeout for use with external OLEDB connections in seconds.

OLAP\Process\DatabaseConnectionPoolMax

50

A signed 32-bit integer property that specifies the maximum number of pooled database connections.

OLAP\Process\DatabaseConnectionPoolTimeout

120000

It is advised that this advanced property not be changed, except under the guidance of Microsoft support.

OLAP\Process\DeepCompressValue

1

An int property applying to measures with Double data type that specifies whether numbers can be compressed, causing a loss in numeric precision. A value of False indicates no compression and no precision loss.

OLAP\Process\IndexBuildThreshold

4096

A signed 32-bit integer property that specifies a row count threshold below which indexes will not be built for partitions.

OLAP\Process\RecordsReportGranularity

10000

A signed 32-bit integer property that specifies how often the server records Trace events during processing, in rows.

OLAP\Process\ROLAPDimensionProcessingEffort

300000

It is advised that this advanced property not be changed, except under the guidance of Microsoft support.

OLAP\ProcessPlan\EnableRolapDimQueryTableGrouping

1

A Boolean property that specifies whether table grouping is enabled for ROLAP dimensions. If true, when querying ROLAP dimensions at runtime, entire ROLAP dimension tables are queried at once, as opposed to separate queries for each attribute.

OLAP\ProcessPlan\MemoryLimitErrorEnabled

true

It is advised that this advanced property not be changed, except under the guidance of Microsoft support.

OLAP\Query\DefaultDrillthroughMaxRows

10000

A signed 32-bit integer property that specifies the maximum number of rows that will return from a drillthrough query.

OLAP\Query\DisableCalcExpressNonEmpty

0

It is advised that this advanced property not be changed, except under the guidance of Microsoft support.

OLAP\Query\NonEmptyBehaviorMode

1

Defines default for Non_Empty_behavior MDX property.

OLAP\Query\RowsetSerializationLimit

-1

A signed 32-bit integer property that defines the maximum number of rows that are serialized in an XMLA response that contains a rowset.

A negative value indicates that there is no limit. A positive value specifies the maximum number of rows.

OLAP\Query\QueryOptimizerRatio

-1

It is advised that this advanced property not be changed, except under the guidance of Microsoft support.

Security\BuiltinAdminsAreServerAdmins

true

When true, indicates that members of the local machine administrators group are Analysis Services administrators; otherwise, false.

Security\CellPermissionMode

0

It is advised that this advanced property not be changed, except under the guidance of Microsoft support.

Security\DataProtection\RequiredProtectionLevel

1

A signed 32-bit integer property that defines the required protection level for all client requests. This property can have one of the following values:

  • 0 – None disabled

  • 1 – Encryption required

  • 2 –Clear-text requests allowed but only with signatures

Security\DisableClientImpersonation

false

When true, indicates that client impersonation (for example, from stored procedures) is disabled; otherwise, false.

Security\RequireClientAuthentication

true

When true, indicates that client authentication is required; otherwise, false.

Security\SecurityPackageList

Empty

A string property that contains a comma-separated list of SSPI packages used by server for client authentication.

Security\ServiceAccountIsServerAdmin

true

When true, indicates that the service account is a server administrator; otherwise, false.

ThreadPool\SchedulingBehavior

-1

An integer that specifies how tasks are scheduled in the thread pools. This property can have one of the following values:

  • -1 – The engine will choose the default behavior.

  • 0 – First in, first out (FIFO). Tasks are run in the order in which they are submitted.

  • 1 – Short query bias. The engine gradually throttles long-running queries when under pressure in favor of fast queries.

ThreadPool\Process\MaxThreads

0

The default value of 0 causes the server to choose a dynamic default based on system hardware properties.

In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the default value is 64.

The target maximum number of threads for the thread pool used by processing operations.

In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, where the default is 64, if a value less than 64 is specified, the server will use the default value.

ThreadPool\Process\MinThreads

0

The default value of 0 causes the server to choose a dynamic default based on system hardware properties.

In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the default value is 1.

The minimum number of threads for the thread pool used by processing operations.

ThreadPool\Query\MaxThreads

0

The default value of 0 causes the server to choose a dynamic default based on system hardware properties.

In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the default value is 10.

A signed 32-bit integer property that defines the maximum number of threads.

ThreadPool\Query\MinThreads

0

The default value of 0 causes the server to choose a dynamic default based on system hardware properties.

In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the default value is 1.

A signed 32-bit integer property that defines the minimum number of threads for queries.

ASPaaS\AlwaysUseGateway

false

When true, indicates that all data sources are accessed through the on-premises data gateway; otherwise, false.

JsonErrorMode

-1

The default value of -1, as well as 1, causes the server to propagate an error code and raise an error.

A value of 0 causes the server to raise a general error.

A signed 32-bit integer property that controls whether to format a JSON error.

ResourceGovernance\DecayIntervalCPUTime

60000

An integer representing the CPU time in milliseconds that a query spends before it decays. If the system is under CPU pressure, decayed queries are limited to the remaining cores that are not reserved for fast queries.

The default value is 60,000, which represents 1 minute of CPU time, not elapsed calendar time.

ResourceGovernance\ReservedComputeForFastQueries

75

An integer between 0 and 100. The unit of measure is the percentage of cores that are reserved for fast queries.

For example, a value of 50 on a server with 32 cores reserves 16 cores for fast queries. This property rounds up to the number of cores. In the example, a value of 51 on a server would round up to 17 cores.

ResourceGovernance\ReservedComputeForProcessing

75

An integer between 0 and 100. The unit of measure is the percentage of cores reserved for fast queries that are reserved for any other processing request in a Tabular model.

For example, on a server with 32 cores, if the value of the ResourceGovernance\ReservedComputeForFastQueries property is 50 and the value of the ResourceGovernance\ReservedComputeForProcessing property is 50, 16 cores are reserved for fast queries and 8 cores are reserved for any other processing requests in a Tabular model. This property rounds up to the number of cores.

<53> Section 2.2.4.2.2.4: If LogFileSize is set to a negative value, the result for Analysis Services is undetermined.

<54> Section 2.2.4.2.2.4: The Filter element is not supported by SQL Server 2005 Analysis Services.

<55> Section 2.2.4.2.2.4.3: The event_session element is not supported by SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2.

<56> Section 2.2.4.2.2.4.3.1: The event element is not supported by SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2.

<57> Section 2.2.4.2.2.4.3.2: The action element is not supported by SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2.

<58> Section 2.2.4.2.2.4.3.3: The target element is not supported by SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2.

<59> Section 2.2.4.2.2.4.3.4: The objectNames attribute group is not supported by SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2.

<60> Section 2.2.4.2.2.4.3.5: The parameter element is not supported by SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2.

<61> Section 2.2.4.2.2.4.3.6: The unary_expr complex type is not supported by SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2.

<62> Section 2.2.4.2.2.4.3.6:  DISCOVER_XEVENT_OBJECTS is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014.

<63> Section 2.2.4.2.2.5: To create a Database object on the server in Analysis Services, both the Name and ID elements need to be specified for the server to return a response with a success message. However, in Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017, only the Name element is required to create a Database object and result in a success-message response.

<64> Section 2.2.4.2.2.5: Analysis Services supports the LCID values that are described in the following table.

Language

LCID

Neutral

0

Arabic

1025

Bulgarian

1026

Catalan

1027

Chinese - Traditional

1028

German

1031

English-US

1033

French

1036

Hebrew

1037

Icelandic

1039

Italian

1040

Japanese

1041

Korean

1042

Dutch

1043

Norwegian (Bokmål)

1044

Brazilian

1046

Romanian

1048

Russian

1049

Croatian

1050

Slovak

1051

Swedish

1053

Thai

1054

Urdu

1056

Indonesian

1057

Ukrainian

1058

Slovenian

1060

Latvian

1062

Lithuanian

1063

Vietnamese

1066

Hindi

1081

Malay - Malaysia

1086

Bengali

1093

Punjabi

1094

Gujarati

1095

Tamil

1097

Telugu

1098

Kannada

1099

Malayalam

1100

Marathi

1102

Chinese - Simplified

2052

British English

2057

Portuguese

2070

Serbian (Latin)

2074

Chinese (Hong Kong SAR, PRC)

3076

Spanish

3082

Serbian (Cyrillic)

3098

Chinese (Singapore)

4100

Chinese (Macau SAR)

5124

<65> Section 2.2.4.2.2.5: Analysis Services uses the value provided by the server administrator in the server configuration file as the default if the language value is empty.

<66> Section 2.2.4.2.2.5: The CompatibilityLevel property is not supported by SQL Server 2005 Analysis Services or SQL Server 2008 Analysis Services. SQL Server 2008 R2 Analysis Services does not support a compatibility level set to greater than 1050. SQL Server 2012 Analysis Services and SQL Server 2014 Analysis Services do not support a compatibility level set to greater than 1103. SQL Server 2016 Analysis Services does not support a compatibility level set to greater than 1200. SQL Server 2017 Analysis Services does not support a compatibility level set to greater than 1400. SQL Server 2019 Analysis Services does not support a compatibility level set to greater than 1500.

<67> Section 2.2.4.2.2.8: For the Type element, the server that is running Analysis Services implements functionality for the enumeration values "Accounts" and "Time". All other enumeration values are only informational.

<68> Section 2.2.4.2.2.8: Analysis Services uses the value provided by the server administrator in the server configuration file as the default if the language value is empty.

<69> Section 2.2.4.2.2.8: Enhanced string handling capabilities are not supported by SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2. The enhancements include allowing for a larger number of strings and a longer length of strings.

<70> Section 2.2.4.2.2.8.1: The ProcessingState element is not supported by SQL Server 2005 and SQL Server 2008.

<71> Section 2.2.4.2.2.8.1: The AttributeHierarchyProcessingState element is not supported by SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2.

<72> Section 2.2.4.2.2.8.1: The ImageUrl enumeration value is not supported by SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2.

<73> Section 2.2.4.2.2.8.1: The ExtendedType enumeration value and the ExtendedType property are not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<74> Section 2.2.4.2.2.8.2: The MemberKeysUnique element is not supported by SQL Server 2005 and Microsoft SQL Server 2005 Service Pack 1 (SP1).

<75> Section 2.2.4.2.2.8.3: The Relationship complex type is not supported by SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2.

<76> Section 2.2.4.2.2.9: Analysis Services uses the value provided by the server administrator in the server configuration file as the default if this value is empty.

<77> Section 2.2.4.2.2.9: The Collation element uses the Analysis Services form of a character set name followed by an underscore (_) character, followed by the sorting sequence name. For more information about Analysis Services collation, see [MSDN-LCAS].

<78> Section 2.2.4.2.2.9: The DaxOptimizationMode element is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017.

<79> Section 2.2.4.2.2.9.1: Analysis Services implicitly includes any attributes not specified in the collection with their default values.

<80> Section 2.2.4.2.2.9.1: Analysis Services implicitly includes hierarchies not specified in the collection with their default values.

<81> Section 2.2.4.2.2.9.4: Analysis Services provides list of known graphics such as arrow and chart; however, other values are possible.

<82> Section 2.2.4.2.2.9.4: Analysis Services provides a list of known values; however, other values are possible.

<83> Section 2.2.4.2.2.10.1: Analysis Services uses the value provided by the server administrator in the server configuration file as the default if this value is empty.

<84> Section 2.2.4.2.2.10.3: The Annotations element is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<85> Section 2.2.4.2.2.11.1.2: In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, and SQL Server 2016, the default value of Cardinality is "Many".

<86> Section 2.2.4.2.2.11.1.2: Analysis Services populates attributes that are not specified in the collection with default element values.

<87> Section 2.2.4.2.2.11.3: This is the RGB format that is used in the Windows operating system.

<88> Section 2.2.4.2.2.11.3: This is the RGB format that is used in the Windows operating system.

<89> Section 2.2.4.2.2.13: Enhanced string handling capabilities are not supported by SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2. The enhancements include allowing for a larger number of strings and a longer length of strings.

<90> Section 2.2.4.2.2.14.1.1: The DefaultMember element is not used in Analysis Services.

<91> Section 2.2.4.2.2.15: The MiningStructure complex type is supported only by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<92> Section 2.2.4.2.2.15: Analysis Services uses the value provided by the server administrator in the server configuration file as the default if this value is empty.

<93> Section 2.2.4.2.2.16: The MiningModel complex type is supported only by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<94> Section 2.2.4.2.2.16: Analysis Services supports the following values for the Algorithm element:

  • Microsoft_Decision_Trees

  • Microsoft_Naive_Bayes

  • Microsoft_Clustering

  • Microsoft_Neural_Network

  • Microsoft_Logistic_Regression

  • Microsoft_Linear_Regression

  • Microsoft_Association_Rules

  • Microsoft_Time_Series

  • Microsoft_Sequence_Clustering

<95> Section 2.2.4.2.2.16: The FoldingParameters element is not supported by SQL Server 2005.

<96> Section 2.2.4.2.2.16: The Filter element is not supported by SQL Server 2005.

<97> Section 2.2.4.2.2.16.1: Analysis Services supports certain ModelingFlag values as built in to algorithms included in the server, such as MODEL_EXISTENCE_ONLY and REGRESSOR.

<98> Section 2.2.4.2.2.16.2: When the value of Usage is "None", Analysis Services does not send any value to the server by default. Therefore, the Usage attribute is not included in the request/response.

<99> Section 2.2.4.2.2.16.2: The Filter element is not supported by SQL Server 2005.

<100> Section 2.2.4.2.2.16.4: The FoldingParameters element is not supported by SQL Server 2005.

<101> Section 2.2.4.2.2.16.4: The FoldIndex element is not supported by SQL Server 2005.

<102> Section 2.2.4.2.2.16.4: The FoldCount element is not supported by SQL Server 2005.

<103> Section 2.2.4.2.2.16.4: The FoldMaxCases element is not supported by SQL Server 2005.

<104> Section 2.2.4.2.2.16.4: The FoldTargetAttribute element is not supported by SQL Server 2005.

<105> Section 2.2.4.2.2.17: Microsoft does not guarantee that the Annotation\Name element produced by Microsoft products is in a style that references the vendor's XML namespace, although in many cases, it might be so.

<106> Section 2.2.4.2.2.17: Analysis Services ignores the Visibility element.

<107> Section 2.2.4.2.2.17.1: The LinguisticSchemas annotation is not supported by SQL Server.

<108> Section 2.2.4.2.2.17.1.1: The LinguisticSchema complex type is not supported by SQL Server.

<109> Section 2.2.4.2.2.17.1.1.1: The EntityType complex type is not supported by SQL Server.

<110> Section 2.2.4.2.2.19: For the Automatic value of NullProcessing, a server that is running Analysis Services uses "ZeroOrBlank" (for OLAP) and "UnknownMember" (for DM).

<111> Section 2.2.4.2.2.20.25: In Analysis Services, the RowNumberBinding type can be used only if the Database, Cube, or MeasureGroup uses memory storage mode.

<112> Section 2.2.4.2.2.21: For DimensionPermission, "None" is not an allowed value for the Read element. However, the server does not reject this value, but automatically changes the value "None" to "Allowed", which is always returned by a query that returns the current value.

<113> Section 2.2.4.2.2.24: The AllowedRowsExpression element can be set only for Tabular projects on a server that is running Analysis Services and cannot be set for any table within an Microsoft Office Excel workbook (regardless of whether or not it is on SharePoint), nor for any MOLAP dimension. For more information about installing Analysis Services in Tabular mode, see [MSDN-InstallASTabMode].

<114> Section 2.2.4.2.2.25: The MiningStructurePermission complex type is supported only by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<115> Section 2.2.4.2.2.26: The MiningModelPermission complex type is supported only by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<116> Section 2.2.4.2.2.31: In Analysis Services, the behavior of the value "Default" is dependent upon the context in which impersonation is used.

<117> Section 3.1.3.1: Analysis Services supports sessions.

<118> Section 3.1.3.1: Analysis Services ends sessions automatically after a period of inactivity that can be configured by the server administrator by using the MinIdleSessionTimeout property.

<119> Section 3.1.3.2: Analysis Services supports sessions.

<120> Section 3.1.3.2: Analysis Services ends sessions automatically after a period of inactivity that can be configured by the server administrator by using the MinIdleSessionTimeout property.

<121> Section 3.1.4.2.1.1: Analysis Services ignores the HTTP header's SOAP action value.

<122> Section 3.1.4.2.2.1.2.1: Analysis Services ignores this value, and it is always treated as if "TupleFormat" were specified.

<123> Section 3.1.4.2.2.1.2.1: Although the expected value for ProviderType is 0x00000003L, Analysis Services always returns the value 0x00000006L.

<124> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "512" for SQLSupport.

<125> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "1" for CatalogLocation.

<126> Section 3.1.4.2.2.1.2.1: Analysis Services returns the value "Database" for DbpropCatalogTerm.

<127> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "0" for DbpropCatalogUsage.

<128> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "0" for DbpropColumnDefinition.

<129> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "1" for DbpropConcatNullBehavior.

<130> Section 3.1.4.2.2.1.2.1: Analysis Services returns the value false for DbpropDataSourceReadOnly.

<131> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "2" for DbpropGroupBy.

<132> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "0" for DbpropHeterogeneousTables.

<133> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "8" for DbpropIdentifierCase.

<134> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "0" for DbpropMaxIndexSize.

<135> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "0" for DbpropMaxOpenChapters.

<136> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "0" for DbpropMaxRowSize.

<137> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value true for DbpropMaxRowSizeIncludeBlob.

<138> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "1" for DbpropMaxTablesInSelect.

<139> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value false for DbpropMultiTableUpdate.

<140> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "4" for DbpropNullCollation.

<141> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value false for DbpropOrderByColumnsInSelect.

<142> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "1" for DbpropOutputParameterAvailable.

<143> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "4" for DbpropPersistentIdType.

<144> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "1" for DbpropPrepareAbortBehavior.

<145> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "1" for DbpropPrepareCommitBehavior.

<146> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "Calculated member" for DbpropProcedureTerm.

<147> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "8" for DbpropQuotedIdentifierCase.

<148> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "0" for DbpropSchemaUsage.

<149> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "512" for DbpropSqlSupport.

<150> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "0" for DbpropSubqueries.

<151> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "0" for DbpropSupportedTxnDdl.

<152> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "4096" for DbpropSupportedTxnIsoLevels.

<153> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "292" for DbpropSupportedTxnIsoRetain.

<154> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "Cube" for DbpropTableTerm.

<155> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "4" for MdpropAggregateCellUpdate.

<156> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "2147483647" for MdpropAxes.

<157> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "1" for MdpropFlatteningSupport.

<158> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "3" for MdpropMdxCaseSupport.

<159> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "7" for MdpropMdxDescFlags.

<160> Section 3.1.4.2.2.1.2.1: MDPROPVAL_MDF_ASYMMETRIC is not supported by Analysis Services in SQL Server 2005 and SQL Server 2005 SP1.

<161> Section 3.1.4.2.2.1.2.1: MDPROPVAL_MDF_CALC_MEMBERS is not supported by Analysis Services in SQL Server 2005 and SQL Server 2008.

<162> Section 3.1.4.2.2.1.2.1: Analysis Services in SQL Server 2005 and SQL Server 2008 returns the value "3". Otherwise, Analysis Services returns the value "7" for MdpropMdxDrillFunctions.

<163> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "63" for MdpropMdxFormulas.

<164> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "1" for MdpropMdxJoinCubes.

<165> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "15" for MdpropMdxMemberFunctions.

<166> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "0" for MdpropMdxNonMeasureExpressions.

<167> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "2047" for MdpropMdxNumericFunctions.

<168> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "496" for MdpropMdxObjQualification.

<169> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "0" for MdpropMdxOuterReference.

<170> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value true for MdpropMdxQueryByProperty.

<171> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "4" for MdpropMdxRangeRowset.

<172> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "524287" for MdpropMdxSetFunctions.

<173> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "2" for MdpropMdxSlicer.

<174> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "15" for MdpropMdxStringCompop.

<175> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "3" for MdpropNamedLevels.

<176> Section 3.1.4.2.2.1.2.1: Analysis Services always returns the value "Core" for MDXSupport.

<177> Section 3.1.4.2.2.1.2.1: Analysis Services ignores the value for DbpropInitMode.

<178> Section 3.1.4.2.2.1.2.1: Analysis Services attempts to deduce the dialect from the content of the command statement, but uses the value provided in the Dialect property if the command contains a value for this property.

<179> Section 3.1.4.2.2.1.2.1: For MdpropMdxSubqueries, Analysis Services in SQL Server 2005 returns the value "3", in SQL Server 2008 returns the value "15", and in SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014 returns the value "31". Otherwise, Analysis Services returns the value "63".

<180> Section 3.1.4.2.2.1.2.1: MDPROPVAL_MSQ_CALCMEMBERS is not supported by Analysis Services in SQL Server 2005.

<181> Section 3.1.4.2.2.1.2.1: MDPROPVAL_MSQ_CALCMEMBERS2 is not supported by Analysis Services in SQL Server 2005 and SQL Server 2008.

<182> Section 3.1.4.2.2.1.2.1: MDPROPVAL_MSQ_DRILLTHROUGH is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014.

<183> Section 3.1.4.2.2.1.2.1: For DbpropMsmdSubqueries, the values "0" and "1" are not supported by Analysis Services in SQL Server 2005. The value "2" is not supported by Analysis Services in SQL Server 2005 and SQL Server 2008.

<184> Section 3.1.4.2.2.1.2.1: The MdpropMdxDdlExtensions property is not supported by Analysis Services in SQL Server 2005 and SQL Server 2008.

<185> Section 3.1.4.2.2.1.2.1: In Analysis Services, the value "31" is returned for MOLAP servers, and the value "23" is returned for in-memory storage servers.

<186> Section 3.1.4.2.2.1.2.1: The ResponseEncoding property is not supported by Analysis Services in SQL Server 2005 and SQL Server 2008.

<187> Section 3.1.4.2.2.1.2.1: The MemoryLockingMode property is not supported by Analysis Services in SQL Server 2005 and SQL Server 2008.

<188> Section 3.1.4.2.2.1.2.1: The DbpropMsmdOptimizeResponse property is not supported by Analysis Services in SQL Server 2005 and SQL Server 2008.

<189> Section 3.1.4.2.2.1.2.1: The DbpropMsmdActivityID element is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<190> Section 3.1.4.2.2.1.2.1: The DbpropMsmdRequestID element is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<191> Section 3.1.4.2.2.1.2.1: The ReturnAffectedObjects element is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014. It can be set only for Tabular databases that have the compatibility level set to 1200 or greater.

<192> Section 3.1.4.2.2.1.2.1: The DbpropMsmdRequestMemoryLimit element is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017.

<193> Section 3.1.4.2.2.1.2.1: The ApplicationContext element is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017.

<194> Section 3.1.4.2.2.1.3.1.1: Analysis Services includes an asterisk (*) in the ROLES column if the current user is a server administrator or database administrator. Analysis Services includes the system user name as a role if one of the roles uses dynamic security.

<195> Section 3.1.4.2.2.1.3.1.1:  The CLIENTCACHEREFRESHPOLICY element is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017.

<196> Section 3.1.4.2.2.1.3.2.1: In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, any restriction set on TABLE_TYPE in the DBSCHEMA_TABLES request returns all table types (SCHEMA, SYSTEM TABLE, and TABLE), regardless of the types that are specified.

<197> Section 3.1.4.2.2.1.3.2.1: In SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2, any restriction set on TABLE_OLAP_TYPE in the DBSCHEMA_TABLES request returns a response in which the OLAP type is SCHEMA.

<198> Section 3.1.4.2.2.1.3.3.1: Analysis Services does not support COLUMN_HAS_DEFAULT and does not report whether the column has a default.

<199> Section 3.1.4.2.2.1.3.3.1: Analysis Services does not support COLUMN_DEFAULT.

<200> Section 3.1.4.2.2.1.3.3.1: Analysis Services returns the value false for IS_NULLABLE.

<201> Section 3.1.4.2.2.1.3.3.1: Analysis Services returns the value -1 for all numeric types except DBTYPE_CY.

<202> Section 3.1.4.2.2.1.3.3.1: Analysis Services does not support this column and returns NULL.

<203> Section 3.1.4.2.2.1.3.4.1: Analysis Services returns one of the following values:

  • SHORT

  • LONG

  • FLOAT

  • DOUBLE

  • CURRENCY

  • DATE

  • BSTR

  • USHORT

  • ULONG

  • CHAR

  • WCHAR

  • VARIANT

<204> Section 3.1.4.2.2.1.3.4.1: Analysis Services always returns the value true for IS_NULLABLE.

<205> Section 3.1.4.2.2.1.3.4.1: Analysis Services always returns the value "3" for SEARCHABLE.

<206> Section 3.1.4.2.2.1.3.4.1: Analysis Services always returns the value false for FIXED_PREC_SCALE.

<207> Section 3.1.4.2.2.1.3.4.1: Analysis Services always returns the value false for AUTO_UNIQUE_VALUE.

<208> Section 3.1.4.2.2.1.3.4.1: Analysis Services always returns the value false for IS_LONG.

<209> Section 3.1.4.2.2.1.3.4.1: Analysis Services ignores any restriction placed on BEST_MATCH.

<210> Section 3.1.4.2.2.1.3.4.1: Analysis Services always returns the value true for BEST_MATCH.

<211> Section 3.1.4.2.2.1.3.5.1: Analysis Services does not support the concept of schemas and always returns NULL for SCHEMA_NAME in all Discover responses containing this column.

<212> Section 3.1.4.2.2.1.3.5.1: Analysis Services does not store this information and always returns NULL.

<213> Section 3.1.4.2.2.1.3.5.1: Analysis Services does not store this information and always returns NULL.

<214> Section 3.1.4.2.2.1.3.5.1: Analysis Services does not store this information and always returns NULL.

<215> Section 3.1.4.2.2.1.3.5.1: Analysis Services always returns the value true for the IS_DRILLTHROUGH_ENABLED column.

<216> Section 3.1.4.2.2.1.3.5.1: In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the output includes cube objects and does not include dimension objects.

<217> Section 3.1.4.2.2.1.3.5.1: The PREFERRED_QUERY_PATTERNS property is not supported by SQL Server 2005 and SQL Server 2008.

<218> Section 3.1.4.2.2.1.3.5.1: The 0x03 value is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<219> Section 3.1.4.2.2.1.3.6.1: Analysis Services does not support the concept of schemas and always returns NULL for SCHEMA_NAME in all Discover responses that contain the SCHEMA_NAME column.

<220> Section 3.1.4.2.2.1.3.6.1: Analysis Services always returns the value false for the IS_VIRTUAL column.

<221> Section 3.1.4.2.2.1.3.6.2: In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the output includes cube objects and does not include dimension objects.

<222> Section 3.1.4.2.2.1.3.7.1: Analysis Services does not support the concept of schemas and returns NULL for SCHEMA_NAME in all Discover responses that contain the SCHEMA_NAME column.

<223> Section 3.1.4.2.2.1.3.7.1: For Analysis Services providers that generate unique names by qualification, each component of DIMENSION_UNIQUE_NAME is delimited.

<224> Section 3.1.4.2.2.1.3.7.1: Analysis Services always returns a value for the HIERARCHY_NAME column.

<225> Section 3.1.4.2.2.1.3.7.1: Analysis Services always returns the value false for the IS_VIRTUAL column.

<226> Section 3.1.4.2.2.1.3.7.1: Analysis Services returns the value 0x01 for the DIMENSION_UNIQUE_SETTINGS column.

<227> Section 3.1.4.2.2.1.3.7.1: Analysis Services does not support the DIMENSION_MASTER_UNIQUE_NAME column.

<228> Section 3.1.4.2.2.1.3.7.1: Analysis Services returns the value true for the DIMENSION_IS_VISIBLE column. If the dimension is not visible, it will not appear in the schema rowset.

<229> Section 3.1.4.2.2.1.3.7.1: Analysis Services returns the value true for the DIMENSION_IS_SHARED column.

<230> Section 3.1.4.2.2.1.3.7.2: In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the output includes cube objects and does not include dimension objects.

<231> Section 3.1.4.2.2.1.3.8.1: Analysis Services does not support the concept of schemas and always returns NULL for SCHEMA_NAME in all Discover responses that contain the SCHEMA_NAME column.

<232> Section 3.1.4.2.2.1.3.8.1: For Analysis Services providers that generate unique names by qualification, each component of DIMENSION_UNIQUE_NAME is delimited.

<233> Section 3.1.4.2.2.1.3.8.1: Analysis Services returns the LEVEL_NAME column if a caption does not exist.

<234> Section 3.1.4.2.2.1.3.8.2: In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the output includes cube objects and does not include dimension objects.

<235> Section 3.1.4.2.2.1.3.9.1: Analysis Services does not support the concept of schemas and always returns NULL for SCHEMA_NAME in all Discover responses that contain the SCHEMA_NAME column.

<236> Section 3.1.4.2.2.1.3.9.1: Analysis Services returns the value -1 for all numeric types except DBTYPE_CY.

<237> Section 3.1.4.2.2.1.3.9.1: In Analysis Services, folder names are separated by a semicolon and nested folders are indicated by a backslash (\).

<238> Section 3.1.4.2.2.1.3.9.2: In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the output includes cube objects and does not include dimension objects.

<239> Section 3.1.4.2.2.1.3.10.1: Analysis Services does not support the concept of schemas and always returns NULL for SCHEMA_NAME in all Discover responses that contain the SCHEMA_NAME column.

<240> Section 3.1.4.2.2.1.3.10.1: Analysis Services returns the PROPERTY_NAME column if a caption does not exist.

<241> Section 3.1.4.2.2.1.3.10.1: Analysis Services returns the value -1 for all numeric types except DBTYPE_CY.

<242> Section 3.1.4.2.2.1.3.10.2: In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the output includes cube objects and does not include dimension objects.

<243> Section 3.1.4.2.2.1.3.11.1: Analysis Services does not support the concept of schemas and always returns NULL for SCHEMA_NAME in all Discover responses that contain the SCHEMA_NAME column.

<244> Section 3.1.4.2.2.1.3.11.1: In Analysis Services, the member type value 4 (formula) takes precedence over the member type value 3 (measure). For example, if there is a formula (calculated) member on the Measures dimension, Analysis Services returns the value 4 for the MEMBER_TYPE column.

<245> Section 3.1.4.2.2.1.3.11.2: In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the output includes cube objects and does not include dimension objects.

<246> Section 3.1.4.2.2.1.3.12.1: Analysis Services does not support the concept of schemas and always returns NULL for SCHEMA_NAME in all Discover responses that contain the SCHEMA_NAME column.

<247> Section 3.1.4.2.2.1.3.12.2: In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the output includes cube objects and does not include dimension objects.

<248> Section 3.1.4.2.2.1.3.13.1: Analysis Services does not support the concept of schemas and always returns NULL for SCHEMA_NAME in all Discover responses that contain the SCHEMA_NAME column.

<249> Section 3.1.4.2.2.1.3.13.2: In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the output includes cube objects and does not include dimension objects.

<250> Section 3.1.4.2.2.1.3.15.1: Analysis Services does not support the concept of schemas and always returns NULL for SCHEMA_NAME in all Discover responses that contain the SCHEMA_NAME column.

<251> Section 3.1.4.2.2.1.3.15.2: In SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1, the output includes cube objects and does not include dimension objects.

<252> Section 3.1.4.2.2.1.3.16.1: Analysis Services does not support the concept of schemas and always returns NULL for SCHEMA_NAME in all Discover responses that contain the SCHEMA_NAME column.

<253> Section 3.1.4.2.2.1.3.17.1: Analysis Services does not support the concept of schemas and always returns NULL for SCHEMA_NAME in all Discover responses that contain the SCHEMA_NAME column.

<254> Section 3.1.4.2.2.1.3.18.1: Analysis Services does not support the concept of schemas and always returns NULL for SCHEMA_NAME in all Discover responses that contain the SCHEMA_NAME column.

<255> Section 3.1.4.2.2.1.3.19: The DMSCHEMA_MINING_SERVICES rowset is supported only by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<256> Section 3.1.4.2.2.1.3.19.1: Analysis Services populates the SERVICE_TYPE_ID column with one of the following values:

  • DM_SERVICETYPE_CLASSIFICATION (1)

  • DM_SERVICETYPE_CLUSTERING (2)

  • DM_SERVICETYPE_ASSOCIATION (4)

  • DM_SERVICETYPE_DENSITY_ESTIMATE (8)

  • DM_SERVICETYPE_SEQUENCE (16)

<257> Section 3.1.4.2.2.1.3.19.1: Analysis Services ignores the case of the values in the SUPPORTED_DISTRIBUTION_FLAGS column.

<258> Section 3.1.4.2.2.1.3.19.1: Analysis Services ignores the case of the values in the SUPPORTED_INPUT_CONTENT_TYPES column.

<259> Section 3.1.4.2.2.1.3.19.1: Analysis Services ignores the case of the values in the SUPPORTED_PREDICTION_CONTENT_TYPES column.

<260> Section 3.1.4.2.2.1.3.20: The DMSCHEMA_MINING_SERVICE_PARAMETERS rowset is supported only by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<261> Section 3.1.4.2.2.1.3.21: The DMSCHEMA_MINING_FUNCTIONS rowset is supported only by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<262> Section 3.1.4.2.2.1.3.22: The DMSCHEMA_MINING_MODEL_CONTENT rowset is supported only by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<263> Section 3.1.4.2.2.1.3.22.1: Analysis Services does not support the concept of schemas and always returns NULL for MODEL_SCHEMA in all Discover responses that contain the MODEL_SCHEMA column.

<264> Section 3.1.4.2.2.1.3.22.1:  SQL Server 2005 Analysis Services does not support DM_NODE_TYPE_ARIMA_ROOT (27).

<265> Section 3.1.4.2.2.1.3.22.1:  SQL Server 2005 Analysis Services does not support DM_NODE_TYPE_ARIMA_PERIODICSTRUCTURE (28).

<266> Section 3.1.4.2.2.1.3.22.1:  SQL Server 2005 Analysis Services does not support DM_NODE_TYPE_ARIMA_AUTOREGRESSIVE (29).

<267> Section 3.1.4.2.2.1.3.22.1:  SQL Server 2005 Analysis Services does not support DM_NODE_TYPE_ARIMA_MOVINGAVERAGE (30).

<268> Section 3.1.4.2.2.1.3.22.1:  The NODE_GUID column is not supported by Analysis Services and always contains NULL.

<269> Section 3.1.4.2.2.1.3.23: The DMSCHEMA_MINING_MODEL_XML rowset is supported only by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<270> Section 3.1.4.2.2.1.3.23: Analysis Services supports only the following algorithms for the DMSCHEMA_MINING_MODEL_XML rowset:

  • Microsoft Decision Trees algorithm

  • Microsoft Clustering algorithm

All other algorithms result in a fault if the DMSCHEMA_MINING_MODEL_XML rowset is requested.

<271> Section 3.1.4.2.2.1.3.23.1: Analysis Services does not support the concept of schemas and always returns NULL for MODEL_SCHEMA in all Discover responses that contain the MODEL_SCHEMA column.

<272> Section 3.1.4.2.2.1.3.23.1: Analysis Services ignores any restriction placed on MODEL_TYPE.

<273> Section 3.1.4.2.2.1.3.24: The DMSCHEMA_MINING_MODEL_CONTENT_PMML rowset is supported only by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<274> Section 3.1.4.2.2.1.3.24: Analysis Services supports only the following algorithms for the DMSCHEMA_MINING_MODEL_CONTENT_PMML rowset:

  • Microsoft Decision Trees algorithm

  • Microsoft Clustering algorithm

All other algorithms result in a fault if the DMSCHEMA_MINING_MODEL_CONTENT_PMML rowset is requested.

<275> Section 3.1.4.2.2.1.3.24.1: Analysis Services does not support the concept of schemas and always returns NULL for MODEL_SCHEMA in all Discover responses that contain the MODEL_SCHEMA column.

<276> Section 3.1.4.2.2.1.3.24.1: Analysis Services ignores any restriction placed on MODEL_TYPE.

<277> Section 3.1.4.2.2.1.3.25: The DMSCHEMA_MINING_MODELS rowset is supported only by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<278> Section 3.1.4.2.2.1.3.25.1: Analysis Services does not support the concept of schemas and always returns NULL for MODEL_SCHEMA in all Discover responses that contain the MODEL_SCHEMA column.

<279> Section 3.1.4.2.2.1.3.25.1: This column is not supported by Analysis Services; it is always NULL.

<280> Section 3.1.4.2.2.1.3.26: The DMSCHEMA_MINING_COLUMNS rowset is supported only by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<281> Section 3.1.4.2.2.1.3.26.1: Analysis Services does not support the concept of schemas and is always NULL for MODEL_SCHEMA in all Discover responses that contain the MODEL_SCHEMA column.

<282> Section 3.1.4.2.2.1.3.26.1: Analysis Services returns the value -1 for all numeric types except DBTYPE_CY.

<283> Section 3.1.4.2.2.1.3.26.1: This column is not supported by Analysis Services; it always contains NULL.

<284> Section 3.1.4.2.2.1.3.26.1: This column is not supported by Analysis Services; it always contains NULL.

<285> Section 3.1.4.2.2.1.3.26.1: This column is not supported by Analysis Services; it always contains NULL.

<286> Section 3.1.4.2.2.1.3.26.1: This column is not supported by Analysis Services; it always contains NULL.

<287> Section 3.1.4.2.2.1.3.26.1: This column is not supported by Analysis Services; it always contains NULL.

<288> Section 3.1.4.2.2.1.3.26.1: This column is not supported by Analysis Services; it always contains NULL.

<289> Section 3.1.4.2.2.1.3.26.1: This column is not supported by Analysis Services; it always contains NULL.

<290> Section 3.1.4.2.2.1.3.26.1: This column is not supported by Analysis Services; it always contains NULL.

<291> Section 3.1.4.2.2.1.3.26.1: This column is not supported by Analysis Services; it always contains NULL.

<292> Section 3.1.4.2.2.1.3.27: The DMSCHEMA_MINING_STRUCTURES rowset is supported only by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<293> Section 3.1.4.2.2.1.3.27.1: This column is not supported by Analysis Services; it is always NULL.

<294> Section 3.1.4.2.2.1.3.28: The DMSCHEMA_MINING_STRUCTURE_COLUMNS rowset is supported only by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<295> Section 3.1.4.2.2.1.3.28.1: This column is not supported by Analysis Services; it is always NULL.

<296> Section 3.1.4.2.2.1.3.28.1: Analysis Services always returns the value FALSE for the COLUMN_HASDEFAULT column.

<297> Section 3.1.4.2.2.1.3.28.1: Analysis Services does not support the COLUMN_DEFAULT column.

<298> Section 3.1.4.2.2.1.3.28.1: SQL Server Analysis Services returns the value -1 for all numeric types except DBTYPE_CY.

<299> Section 3.1.4.2.2.1.3.28.1: This column is not supported by Analysis Services; it is always NULL.

<300> Section 3.1.4.2.2.1.3.33.1: Analysis Services always returns the values MDP, TDP, and DMP for ProviderType.

<301> Section 3.1.4.2.2.1.3.33.1: Analysis Services always returns the value "Authenticated" for AuthenticationMode. Integrated Security provided by Microsoft Internet Information Services (IIS) is an example of an underlying security mode.

<302> Section 3.1.4.2.2.1.3.40.1: When a restriction is applied to the Shrinkable column, Analysis Services interprets values 0 as false and -1 as true. Any other values result in no rows being returned.

<303> Section 3.1.4.2.2.1.3.43.1: Analysis Services ignores any restriction placed on CONNECTION_IMPERSONATED_USER_NAME.

<304> Section 3.1.4.2.2.1.3.43.1: This column is not supported by Analysis Services; it is always NULL.

<305> Section 3.1.4.2.2.1.3.43.1: Analysis Services ignores any restriction placed on CONNECTION_ELAPSED_TIME_MS.

<306> Section 3.1.4.2.2.1.3.43.1: Analysis Services in SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2 ignores any restriction placed on CONNECTION_LAST_COMMAND_ELAPSED_TIME_MS.

<307> Section 3.1.4.2.2.1.3.43.1: Analysis Services returns only those connections that are currently executing commands and in which the elapsed time since the start of the last command is greater than the specified restriction value.

<308> Section 3.1.4.2.2.1.3.43.1: Analysis Services ignores any restriction placed on CONNECTION_IDLE_TIME_MS.

<309> Section 3.1.4.2.2.1.3.44.1: In Analysis Services, any restriction set on SESSION_ID in a DISCOVER_SESSIONS request always returns an empty response.

<310> Section 3.1.4.2.2.1.3.44.1: Analysis Services ignores any restriction placed on SESSION_ELAPSED_TIME_MS.

<311> Section 3.1.4.2.2.1.3.44.1: Analysis Services supports restrictions on SESSION_IDLE_TIME_MS up to 429,496. Behavior is undefined for larger values of this restriction.

<312> Section 3.1.4.2.2.1.3.44.1: Analysis Services ignores any restriction placed on SESSION_STATUS.

<313> Section 3.1.4.2.2.1.3.48.1: Analysis Services ignores any restriction placed on KEY.

<314> Section 3.1.4.2.2.1.3.49.1: Analysis Services uses the performance counters provided by SQL Server. For more information, see [MSDN-SSPTP].

<315> Section 3.1.4.2.2.1.3.50.1:  An input validation in the product requires the LOCATION_BACKUP_FILE_PATHNAME to be provided as input to the DISCOVER_LOCATIONS request.

<316> Section 3.1.4.2.2.1.3.57.1: Analysis Services ignores any restriction placed on OBJECT_PARENT_PATH.

<317> Section 3.1.4.2.2.1.3.57.1: Analysis Services ignores any restriction placed on OBJECT_ID.

<318> Section 3.1.4.2.2.1.3.57.1: The OBJECT_MEMORY_CHILD_SHRINKABLE column is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<319> Section 3.1.4.2.2.1.3.57.1: The OBJECT_MEMORY_CHILD_NONSHRINKABLE column is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<320> Section 3.1.4.2.2.1.3.57.1: The OBJECT_GROUP column is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012.

<321> Section 3.1.4.2.2.1.3.58: A server that is running Analysis Services has to have the DeploymentMode property set to 2 for DISCOVER_STORAGE_TABLES to function. The DeploymentMode property is set in the msmdsrv.ini file. DISCOVER_PROPERTIES does not return the value of the DeploymentMode property. DISCOVER_STORAGE_TABLES is not supported by Analysis Services in SQL Server 2005 and SQL Server 2008.

<322> Section 3.1.4.2.2.1.3.58.1: SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2 ignore any restriction placed on DATABASE_NAME.

<323> Section 3.1.4.2.2.1.3.58.1: Analysis Services ignores any restriction placed on CUBE_NAME.

<324> Section 3.1.4.2.2.1.3.58.1: Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014 ignores any restriction placed on MEASURE_GROUP_NAME.

<325> Section 3.1.4.2.2.1.3.58.1: Analysis Services ignores any restriction placed on PARTITION_NAME.

<326> Section 3.1.4.2.2.1.3.59: A server that is running Analysis Services has to have the DeploymentMode property set to 2 for DISCOVER_STORAGE_TABLE_COLUMNS to function. The DeploymentMode property is set in the msmdsrv.ini file. DISCOVER_PROPERTIES does not return the value of the DeploymentMode property. DISCOVER_STORAGE_TABLE_COLUMNS is not supported by Analysis Services in SQL Server 2005 and SQL Server 2008.

<327> Section 3.1.4.2.2.1.3.59.1: SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2 ignore any restriction placed on DATABASE_NAME.

<328> Section 3.1.4.2.2.1.3.59.1: Analysis Services ignores any restriction placed on CUBE_NAME.

<329> Section 3.1.4.2.2.1.3.59.1: Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014 ignores any restriction placed on MEASURE_GROUP_NAME.

<330> Section 3.1.4.2.2.1.3.59.1: Analysis Services ignores any restriction placed on DATATYPE.

<331> Section 3.1.4.2.2.1.3.59.1: DICTIONARY_SIZE is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<332> Section 3.1.4.2.2.1.3.59.1:  DICTIONARY_ISPAGEABLE is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<333> Section 3.1.4.2.2.1.3.59.1:  DICTIONARY_ISRESIDENT is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<334> Section 3.1.4.2.2.1.3.59.1:  DICTIONARY_TEMPERATURE is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<335> Section 3.1.4.2.2.1.3.59.1:  DICTIONARY_LAST_ACCESSED is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<336> Section 3.1.4.2.2.1.3.60: A server that is running Analysis Services has to have the DeploymentMode property set to 2 for DISCOVER_STORAGE_TABLE_COLUMN_SEGMENTS to function. The DeploymentMode property is set in the msmdsrv.ini file. DISCOVER_PROPERTIES does not return the value of the DeploymentMode property. DISCOVER_STORAGE_TABLE_COLUMN_SEGMENTS is not supported by Analysis Services in SQL Server 2005 and SQL Server 2008.

<337> Section 3.1.4.2.2.1.3.60.1: SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2 ignore any restriction placed on DATABASE_NAME.

<338> Section 3.1.4.2.2.1.3.60.1: Analysis Services ignores any restriction placed on CUBE_NAME.

<339> Section 3.1.4.2.2.1.3.60.1: Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014 ignores any restriction placed on MEASURE_GROUP_NAME.

<340> Section 3.1.4.2.2.1.3.60.1: ISPAGEABLE is not supported by Analysis Services in SQL Server.

<341> Section 3.1.4.2.2.1.3.60.1: ISRESIDENT is not supported by Analysis Services in SQL Server.

<342> Section 3.1.4.2.2.1.3.60.1: TEMPERATURE is not supported by Analysis Services in SQL Server.

<343> Section 3.1.4.2.2.1.3.60.1: LAST_ACCESSED is not supported by Analysis Services in SQL Server.

<344> Section 3.1.4.2.2.1.3.61: DISCOVER_CSDL_METADATA is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2. For this request type, the deployment mode of the server is set to 0, 1, or 2. Analysis Services in SQL Server 2012 prior to SQL Server 2012 SP1 supports only settings 1 and 2 for DISCOVER_CSDL_METADATA.

<345> Section 3.1.4.2.2.1.3.61: In SQL Server 2012 prior to SQL Server 2012 SP1, the objects are not included in the output.

<346> Section 3.1.4.2.2.1.3.61.2: The VERSION restriction is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<347> Section 3.1.4.2.2.1.3.61.2: The IGNORE_TRANSLATIONS restriction is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<348> Section 3.1.4.2.2.1.3.61.2: The PRINT_ALL_TRANSLATIONS restriction is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<349> Section 3.1.4.2.2.1.3.62: DISCOVER_CALC_DEPENDENCY is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2. For this request type, the deployment mode of the server is set to 0, 1, or 2. Analysis Services in SQL Server 2012 prior to SQL Server 2012 SP1 supports only settings 1 and 2 for DISCOVER_CALC_DEPENDENCY.

<350> Section 3.1.4.2.2.1.3.62.2: The QUERY restriction is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<351> Section 3.1.4.2.2.1.3.62.2: The DATABASE_NAME restriction is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, and SQL Server 2016.

<352> Section 3.1.4.2.2.1.3.62.2: The OBJECT_TYPE restriction is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, and SQL Server 2016.

<353> Section 3.1.4.2.2.1.3.62.2: The OBJECT_CATEGORY restriction is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, and SQL Server 2016.

<354> Section 3.1.4.2.2.1.3.62.2: The KIND restriction is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, and SQL Server 2016.

<355> Section 3.1.4.2.2.1.3.63.1:  In SQL Server Analysis Services, when LIBRARY_NAME is specified, an empty rowset is returned.

<356> Section 3.1.4.2.2.1.3.64:  DISCOVER_RING_BUFFERS is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014.

<357> Section 3.1.4.2.2.1.3.65:  DISCOVER_XEVENT_TRACE_DEFINITION is supported only by Analysis Services in SQL Server 2012 and SQL Server 2014.

<358> Section 3.1.4.2.2.1.3.66:  DISCOVER_XEVENT_PACKAGES is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014.

<359> Section 3.1.4.2.2.1.3.67:  DISCOVER_XEVENT_OBJECTS is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014.

<360> Section 3.1.4.2.2.1.3.68:  DISCOVER_XEVENT_OBJECT_COLUMNS is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014.

<361> Section 3.1.4.2.2.1.3.69:  DISCOVER_XEVENT_SESSIONS is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014.

<362> Section 3.1.4.2.2.1.3.70:  DISCOVER_XEVENT_SESSION_TARGETS is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014.

<363> Section 3.1.4.2.2.1.3.71: DISCOVER_MEM_STATS is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017.

<364> Section 3.1.4.2.2.1.3.71.1: OWNED_STORE_MEMORY_KB is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<365> Section 3.1.4.2.2.1.3.72: DISCOVER_DB_MEM_STATS is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017.

<366> Section 3.1.4.2.2.1.3.72.1: PROXY_REQUESTS_MEMORY_KB is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<367> Section 3.1.4.2.2.1.3.73: DISCOVER_OBJECT_COUNTERS is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<368> Section 3.1.4.3.2.1.1.10: The SubscriptionId element is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017.

<369> Section 3.1.4.3.2.1.1.11: The Unsubscribe command is not supported by SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017.

<370> Section 3.1.4.3.2.1.1.14: DurabilityGuarantee is not supported by SQL Server.

<371> Section 3.1.4.3.2.1.1.16: In Analysis Services, locks are held in the context of the current transaction. When the transaction commits or rolls back, the locks are automatically released.

<372> Section 3.1.4.3.2.1.1.28: Analysis Services does not support the Statement command within a Batch.

<373> Section 3.1.4.3.2.1.1.28: Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014 does not support execution of the Discover command within a Batch.

<374> Section 3.1.4.3.2.1.1.28: With the exception of SQL Server 2005 Analysis Services and SQL Server 2008 Analysis Services, additional empty result sets can be returned. Clients can choose to ignore the additional empty result elements.

<375> Section 3.1.4.3.2.1.1.29: A server that is running Analysis Services has to have the deployment mode set to 1 to be able to execute the ImageLoad command. ImageLoad is not supported by Analysis Services in SQL Server 2005 and SQL Server 2008. The Data/DataBlock element that is used in ImageLoad is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<376> Section 3.1.4.3.2.1.1.30: A server that is running Analysis Services has to have the deployment mode set to 1 to be able to execute the ImageSave command. ImageSave is not supported by Analysis Services in SQL Server 2005 and SQL Server 2008. The Data element that is used in ImageSave is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<377> Section 3.1.4.3.2.1.1.31: A server that is running Analysis Services has to have the deployment mode set to 1 to be able to execute the CloneDatabase command. CloneDatabase is not supported by Analysis Services in SQL Server 2005 and SQL Server 2008. The Data element that is used in CloneDatabase is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<378> Section 3.1.4.3.2.1.1.32: A server that is running Analysis Services has to have the deployment mode set to 1 to be able to execute the SetAuthContext command. SetAuthContext is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 prior to SQL Server 2012 SP1.

<379> Section 3.1.4.3.2.1.1.33: The DBCC command is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014.

<380> Section 3.1.4.3.2.1.1.34: The RemoveDiscontinuedFeatures command is not supported by Analysis Services in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019.

<381> Section 3.2.1: Analysis Services supports one default instance and multiple named instances of the server on a single computer. The default TCP port number for the default instance is 2383. To connect to a named instance, the client first connects to the SQL Browser service on port 2382, gets the list of named instances on the computer by sending a DISCOVER_INSTANCES request, and then examines the response to determine the TCP port number corresponding to the desired named instance.