ArticleDirectory
- Cumulative Update information
Fix: "There is insufficient system memory in resource pool 'internal' to run this query" error message when you run a full-text query that uses Compound Words in Microsoft SQL Server 2008 or in Microsoft SQL server 2008 r2
Http://support.microsoft.com/kb/982854/en-us
Cumulative Update information SQL Server 2008 Service Pack 1
The fix for this issue was first released in cumulative update 9 for SQL Server 2008 Service Pack 1. for more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 2083921Http://support.microsoft.com/kb/2083921/LN)Cumulative Update 9 for SQL Server 2008 Service Pack 1
NoteBecause the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were encoded with the previous SQL Server 2008 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: 970365Http://support.microsoft.com/kb/970365/LN)The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 Hotfixes are created for specific SQL Server service packs. you must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. by default, any hotfix that is provided in a SQL Server Service Pack is supported in the next SQL Server Service Pack.
SQL Server 2008 Service Pack 2
The fix for this issue was first released in cumulative update 1 for SQL Server 2008 Service Pack 2. for more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 2289254Http://support.microsoft.com/kb/2289254)Cumulative Update 1 for SQL Server 2008 Service Pack 2
NoteBecause the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were encoded 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: 2402659(Http://support.microsoft.com/kb/2402659.pdf/)The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released SQL Server 2008 r2
The fix for this issue was first released in cumulative update 4. for more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base: 2345451Http://support.microsoft.com/kb/2345451)Cumulative Update package 4 for SQL Server 2008 r2
NoteBecause the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were encoded with the previous SQL Server 2008 R2 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: 981356Http://support.microsoft.com/kb/981356)The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released