Microsoft KB Archive/917940

= FIX: The prediction performance of the Microsoft Naive Bayes algorithm may be slower than the prediction performance of other algorithms for the same mining model in SQL Server 2005 Analysis Services =

Article ID: 917940

Article Last Modified on 11/4/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Analysis Services

-



BUG #: 50000166 (SQL Hotfix)



Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by the hotfix package
 * The prerequisites for installing the hotfix package
 * Whether you must restart the computer after you install the hotfix package
 * Whether the hotfix package is replaced by any other hotfix package
 * Whether you must make any registry changes
 * The files that are contained in the hotfix package



SYMPTOMS
Consider the following scenario. You develop a Microsoft SQL Server 2005 Analysis Services project by using Business Intelligence Development Studio. You use the Microsoft Naive Bayes algorithm for a mining model that contains a nested input table in Analysis Services. In this scenario, the prediction performance of the Microsoft Naive Bayes algorithm may be slower than the prediction performance of other algorithms for the same mining model.

For example, you can use System Monitor to collect data from the Predictions/sec counter of the MSAS 2005:Data Mining Prediction performance object. If you do this, you notice that the prediction performance of the Microsoft Naive Bayes algorithm is much slower than the prediction performance of other algorithms for the same mining model.

Note For a named instance, the name of the performance object is MSOLAP$ :Data Mining Prediction.



Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
To apply this hotfix, you must have Analysis Services installed on the computer.

Restart information
If the installer must replace files that are being used, you must restart the computer after you apply this hotfix. To avoid restarting the computer, exit all Analysis Services tools and clients. If the computer is configured to provide HTTP access, you must exit Microsoft Internet Information Services (IIS). If you installed Analysis Services as a named instance, you must stop the SQL Server Browser service because the Msmdredir.dll component of the SQL Server Browser service is updated during the installation of this hotfix.

Registry information
You do not have to change the registry.

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

SQL Server 2005 Analysis Services, Itanium architecture version


STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbsql2005bi kbsql2005as kbexpertiseadvanced kbfix kbhotfixserver kbqfe kbpubtypekc KB917940

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.