This document discusses programming SQL Server data mining with Analysis Management Objects (AMO) and stored procedures. It describes how to create mining structures and models using AMO, including defining columns, updating objects, and processing models. It also explains how to create, execute, and debug stored procedures for adding business logic, including registering assemblies, setting permissions, and attaching to processes for debugging. The goal is to provide an overview of programming options for data mining with SQL Server.

1. Programming SQL Server Data Mining

2. overview Data Mining APIs Programming AMO Data Mining Objects Stored Procedures Creating Stored Procedures Executing Stored Procedures Deploying and Debugging Stored Procedure Assemblies Summary

3. Data Mining APIs The major APIs used in Analysis Services programming.

4. Data Mining APIs The major APIs used in Analysis Services programming.

5. Data Mining APIs

7. create the data mining model that supports the mining algorithm you want to use in order to predict or to find the relationships underlying your data.

8. process the mining models to obtain the trained models that you will use later when querying and predicting from the client application.Note: AMO is not for querying; AMO is for managing and administering your mining structures and models. To query your data, use ADOMD.NET

10. Create columns for the model. Each column needs a name and internal ID, a type, a content definition, and a binding.

13. You can write an external routines called by a stored procedure in any common language runtime (CLR) language, such as C, C++, C#, Visual Basic, or Visual Basic .NET.

15. Executing Stored Procedures Server ADOMD.NET allows you to execute DMX queries using the same objects that you would use with ADOMD.NET. The only exception is that you do not have to specify a connection, because you are already connected. You can copy the results from the query into a DataTable, or you can simply return the DataReader returned by ExecuteReader.

16. Deploying and Debugging Stored Procedure Assemblies After Compiling and building the stored procedure, you must deploy the procedure to your Analysis Server in order to call it from DMX. To add a .NET assembly to your Analysis Services project, right-click the Assemblies folder in Solution Explorer and select New Assembly Reference. select some security-related options, such as Permissions and Impersonation information. The Permissions property specifies the code access permissions that are granted to the assembly when it’s loaded by Analysis Services. The recommended (and default) value is Safe.

17. Deploying and Debugging Stored Procedure Assemblies To debug the assembly in Visual Studio, select Attach to Process from the Debug menu. Select the executable msmdsrv.exe from the list, and ensure that the dialog box displays CLR as the Attach To option. you will be able to set breakpoints in your stored procedures at the end.

18. Major Data Mining APIs Programming AMO Data Mining Objects Stored Procedures basics Deploying and Debugging Stored Procedure Assemblies Summary

19. Visit more self help tutorials Pick a tutorial of your choice and browse through it at your own pace. The tutorials section is free, self-guiding and will not involve any additional support. Visit us at www.dataminingtools.net