Data Mining Stored Procedures (Analysis Services - Data Mining)

  • Artikel

Applies to: SQL Server 2019 and earlier Analysis Services Azure Analysis Services Fabric/Power BI Premium

Important

Data mining was deprecated in SQL Server 2017 Analysis Services and now discontinued in SQL Server 2022 Analysis Services. Documentation is not updated for deprecated and discontinued features. To learn more, see Analysis Services backward compatibility.

Beginning in SQL Server 2005 (9.x), SQL Server Analysis Services supports stored procedures that can be written in any managed language. The managed languages that are supported include Visual Basic .NET, C#, and managed C++. In SQL Server Management Studio, you can call the stored procedures directly by using the CALL statement, or as part of a Data Mining Extensions (DMX) query.

For more information about calling SQL Server Analysis Services stored procedures, see Calling Stored Procedures.

For general information about programmability, see Data Mining Programming.

For additional information about how to program data mining objects, see the article, "SQL Server Data Mining Programmability", in the MSDN library.

Note

When you query mining models, especially when you test new data mining solutions, you might find it convenient to call the system stored procedures that are used internally by the data mining engine. You can view the names of these system stored procedures by using SQL Server Profiler to create a trace on the SQL Server Analysis Services server, and then creating, browsing, and querying the data mining models. However, Microsoft does not guarantee the compatibility of system stored procedures between versions, and you should never use calls to the system stored procedures in a production system. Instead, for compatibility, you should create your own queries by using DMX or XML/A.

In This Section

See Also

Cross-Validation (Analysis Services - Data Mining)
Cross-Validation Tab (Mining Accuracy Chart View)
Calling a Stored Procedure