About plug-in algorithms in SQL Server 2005

Hi, all here,

I am having a question about plug-in algorithms in SQL Server 2005. Since we are able to implement our own algorithms in SQL Server 2005 analysis services architecture, so my question is: what benefits can to a great extent be achieved? Like say, we are going to implement a plug-in algorithm, so what considerations should be concerned?

Thanks a lot in advance for any guidance and help.

The plug-in architecture allows you to implement any algorithm that consumes data in attribute value pairs. Analysis Services takes care of many infrastructure needs so that your development can focus on what's important to you - the details of the algorithm.

For example, AS takes care of

data access, pulling the data from a variety of sources|||Hi, Jamie, thanks a lot.|||This white paper provides an overview of the benefits of the plug-in architecture , along with links to more technical resources: Add Custom Data Mining Algorithms to SQL Server 2005.|||

Hi, Raman, Thanks a lot.

In addition, would you please make sure that what languages are supported in data mining plug-in framework for implementation? Thanks a lot.

|||The plug-in infrastructure passes on client locale information as appropriate in the contextservices object but it's up to you as the algorithm implementor to return the appropriate localized strings (and numbers, as the case may be). Ideally, plug-in algorithms should support all 10 languages supported by SQL Server 2005 Analysis Services.|||Hi, Raman, thanks a lot.

About Data algorithms

I just want to know what are the data algorithms available for sql server 2005 and can i use data mining as a web service

A list of algorithms with descriptions can be found at this location: http://msdn2.microsoft.com/en-us/library/ms175595.aspx

SQL Server Data Mining can be used as a web service (by sending XML/A requests inside SOAP payloads). A (live) sample for this can be found here: http://www.sqlserverdatamining.com/XMLAThinMiner/

Our client APIs (OLE DB Provider for Analysis Services, Adomd.Net, AMO) can also be used to conect to an Analysis Services HTTP end point. In this context, the web service communication part is encapsulated in our APIs, so your application does not need to distinguish between locally-accessible servers and HTTP end points (other than providing the appropriate connection string)