| title | OPENQUERY (DMX) |
|---|---|
| description | <source data query> - OPENQUERY |
| ms.date | 02/17/2022 |
| ms.service | sql |
| ms.subservice | analysis-services |
| ms.topic | reference |
| ms.custom | dmx |
[!INCLUDEssas]
Replaces the source data query with a query to an existing data source. The INSERT, SELECT FROM PREDICTION JOIN, and SELECT FROM NATURAL PREDICTION JOIN statements support OPENQUERY.
OPENQUERY(<named datasource>, <query syntax>)
named datasource
A data source that exists on the [!INCLUDEmsCoName] [!INCLUDEssNoVersion] [!INCLUDEssASnoversion] database.
query syntax
A query syntax that returns a rowset.
OPENQUERY provides a more secure way to access external data by supporting data source permissions. Because the connection string is stored in the data source, administrators can use the properties of the data source to manage access to the data. For more information about data sources, see Supported Data Sources (SSAS - Multidimensional).
You can get a list of the data sources that are available on a server by querying the MDSCHEMA_INPUT_DATASOURCES schema rowset. For more information about using MDSCHEMA_INPUT_DATASOURCES, see MDSCHEMA_INPUT_DATASOURCES Rowset.
You can also return a list of data sources in the current Analysis Services database by using the following DMX query:
SELECT * FROM $system.MDSCHEMA_INPUT_DATASOURCES
The following example uses the MyDS data source already defined in the [!INCLUDEssASnoversion] database to create a connection to the [!INCLUDE sssampledbdwobject-md] database and query the vTargetMail view.
OPENQUERY (MyDS,'SELECT TOP 1000 * FROM vTargetMail')
<source data query>
Data Mining Extensions (DMX) Data Manipulation Statements
Data Mining Extensions (DMX) Statement Reference