| title | ADOMD.NET Server Functionality | Microsoft Docs | ||
|---|---|---|---|
| ms.custom | |||
| ms.date | 03/06/2017 | ||
| ms.prod | sql-server-2014 | ||
| ms.reviewer | |||
| ms.technology | analysis-services | ||
| ms.topic | reference | ||
| helpviewer_keywords |
|
||
| ms.assetid | b74c6957-3f64-4e09-aa09-d06ee93f82fa | ||
| author | minewiskan | ||
| ms.author | owend | ||
| manager | craigg |
All ADOMD.NET server objects provide read-only access to the data and metadata on the server. To retrieve data and metadata, you use the ADOMD.NET server object model as the server object model does not support schema rowsets.
With ADOMD.NET server objects, you can create a user defined function (UDF) or a stored procedure for [!INCLUDEmsCoName] [!INCLUDEssNoVersion] [!INCLUDEssASnoversion]. These in-process methods are called through query statements created in languages such as Multidimensional Expressions (MDX), Data Mining Extensions (DMX), or SQL. These in-process methods also provide added functionality without the latencies associated with network communications.
Note
The xref:Microsoft.AnalysisServices.AdomdServer.AdomdCommand object only supports DMX.
A UDF is a method that has the following characteristics:
-
You can call the UDF in the context of a query.
-
The UDF can take any number of parameters.
-
The UDF can return various types of data.
The following example uses the fictional UDF, FinalSalesNumber:
SELECT SalesPerson.Name ON ROWS,
FinalSalesNumber() ON COLUMNS
FROM SalesModel
A stored procedure is a method that has the following characteristics:
-
You call a stored procedure on its own with the MDX CALL statement.
-
A stored procedure can take any number of parameters.
-
A stored procedure can return a dataset, an
IDataReader, or an empty result.
The following example uses the fictional stored procedure, FinalSalesNumbers:
CALL FinalSalesNumbers()