Article ID: 968290 - Last Review: May 18, 2009 - Revision: 2.0 FIX: A mining model of the Microsoft Decision Tree algorithm generates incorrect nodes when you set the MINIMUM_SUPPORT parameter to "9" in SQL Server 2005 Analysis Services or in SQL Server 2008 Analysis ServicesMicrosoft 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. Microsoft distributes Microsoft SQL Server 2008 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 2008 fix release. On This PageSYMPTOMSIn Microsoft SQL Server 2005 Analysis Services or in Microsoft SQL Server 2008 Analysis Services, you create a mining model by using the Microsoft Decision Tree algorithm. You set the MINIMUM_SUPPORT parameter for the Microsoft Decision Trees algorithm to 9 instead of the default value 10. When you run a Data Mining Extensions (DMX) query on the mining model, you find that extra nodes are generated incorrectly. RESOLUTIONCumulative update information for SQL Server 2005 Service Pack 3The fix for this issue was first released in Cumulative Update 3 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:967909
(http://support.microsoft.com/kb/967909/LN/
)
Cumulative update package 3 for SQL Server 2005 Service Pack 3 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:960598
(http://support.microsoft.com/kb/960598/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Cumulative update information for SQL Server 2008The fix for this issue was first released in Cumulative Update 5 for SQL Server 2008. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:969531
(http://support.microsoft.com/kb/969531/
)
Cumulative update package 5 for SQL Server 2008 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:956909
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was released Cumulative update information for SQL Server 2008 Service Pack 1The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 Service Pack 1. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:970315
(http://support.microsoft.com/kb/970315/
)
Cumulative update package 2 for SQL Server 2008 Service Pack 1 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:970365
(http://support.microsoft.com/kb/970365/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base: 967909
(http://support.microsoft.com/kb/967909/LN/
)
Cumulative update package 3 for SQL Server 2005 Service Pack 3 For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:969531
(http://support.microsoft.com/kb/969531/LN/
)
Cumulative update package 5 for SQL Server 2008 For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:970315
(http://support.microsoft.com/kb/970315/LN/
)
Cumulative update package 2 for SQL Server 2008 Service Pack 1 REFERENCES
For more information about the list of builds that are available after SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
960598
(http://support.microsoft.com/kb/960598/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
For more information about the list of builds that are available after SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
956909
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was released
For more information about the list of builds that are available after SQL Server 2008 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
970365
(http://support.microsoft.com/kb/970365/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
913089
(http://support.microsoft.com/kb/913089/
)
How to obtain the latest service pack for SQL Server 2005
For more information about the new features in SQL Server 2005 SP3 and about the improvements in SQL Server 2005 SP3, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=131442
(http://go.microsoft.com/fwlink/?LinkId=131442)
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
(http://support.microsoft.com/kb/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
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
| Article Translations
|
Back to the top
