Select the product you need help with
FIX: The full-text index population for the indexed view is very slow in SQL Server 2005Article ID: 928537 - View products that this article applies to. Bug #: 50000484 (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. On This PageSUMMARYThis article describes the following about this hotfix release:
SYMPTOMS Consider the following scenario. In Microsoft SQL Server 2005, you create a full-text index on an indexed view. The indexed view contains many rows. Then, you perform a full-text index population for the indexed view. In this scenario, the full-text index population for the indexed view is very slow. If you perform the full-text index population for an indexed table that contains the same rows and the same structure, the full-text index population for the indexed table is much faster. CAUSEThis problem occurs because the SQL Server 2005 query optimizer may not use the index on the view. This problem occurs when the Microsoft Full-Text Engine for SQL Server (MSFTESQL) service runs a query to retrieve data from the indexed view. RESOLUTIONService pack informationThis problem was fixed in SQL Server 2005 Service Pack 2 (SP2). For more information, click the following article number to view the article in the Microsoft Knowledge Base:913089
To resolve this problem, obtain the latest service pack for SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/913089/
)
How to obtain the latest service pack for SQL Server 2005
913089
(http://support.microsoft.com/kb/913089/
)
How to obtain the latest service pack for SQL Server 2005
Hotfix informationA supported hotfix is 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 software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
Prerequisites
Restart informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have to change the registry.Hotfix file informationThis 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 32-bit versionCollapse this table
SQL Server 2005 x64-based versionCollapse this table
SQL Server 2005 Itanium architecture versionCollapse this table
Trace flag informationAfter you apply this hotfix, you must add the -T7614 option as a SQL Server startup parameter to enable trace flag 7614. Then, you must restart the SQL Server service.For more information about how to add SQL Server startup parameters, see the "To start an instance of SQL Server with startup options" section in the "How to start an instance of SQL Server (SQL Server Configuration Manager)" topic in SQL Server 2005 Books Online. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" 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
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
PropertiesArticle ID: 928537 - Last Review: October 8, 2011 - Revision: 3.0 APPLIES TO
|



Back to the top








