Not an IT pro?

We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second.

Understanding the DMX Select Statement

Understanding the DMX Select Statement

Updated: March 2, 2016

The
SELECT statement is the basis for most queries that you create with Data Mining Extensions (DMX) in Microsoft SQL Server Analysis Services. It can perform many different kinds of tasks, such as browsing and predicting against data mining models.

Following are the tasks that you can complete by using the SELECT statement:

Browse a data mining model. The schema rowset defines the structure of a model.

Discover the possible values of a mining model column.

Browse the cases that are assigned to nodes in a mining model, or get a representative case.

Create predictions using a variety of inputs.

Copy mining models.

Each of these tasks uses a different set of data, which we’ll call a data domain. You define the data domain in the FROM clause of the statement.

You want to find objects in the data mining model itself, such as the rule that defines a set of data, or a formula used to make predictions.

In that case, you need to look at the metadata that is stored in the model itself. Therefore, your data domain is the columns in the data mining schema rowset.

You want to get detailed information from the cases used to build the model.

In that case, you need to drill through to the mining structure, which is your data domain, and look at individual rows in columns such as Gender, Bike Buyer, and so on.

IMPORTANT: Anything that is included in the expression list or in the WHERE clause must come from the data domain that is defined by the FROM clause. You cannot mix data domains.