Microsoft KB Archive/928537

= FIX: The full-text index population for the indexed view is very slow in SQL Server 2005 =

Article ID: 928537

Article Last Modified on 1/2/2008

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems

-



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.



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. 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.



CAUSE
This 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.



Service pack information
This problem was fixed in SQL Server 2005 Service Pack 2 (SP2). For more information about SQL Server 2005 SP2, click the following article number 913089 to view the article 913089 in the Microsoft Knowledge Base:

How to obtain the latest service pack for SQL Server 2005

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:

913089 How to obtain the latest service pack for SQL Server 2005

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
 SQL Server 2005 Service Pack 1 (SP1)

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

913089 How to obtain the latest service pack for SQL Server 2005



Restart information
You do not have to restart the computer after you apply 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.

Trace flag information
After 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 &quot;To start an instance of SQL Server with startup options&quot; section in the &quot;How to start an instance of SQL Server (SQL Server Configuration Manager)&quot; topic in SQL Server 2005 Books Online.



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: kbexpertiseadvanced kbtshoot kbfix kbsql2005fts kbhotfixserver kbqfe kbpubtypekc KB928537

-

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

© Microsoft Corporation. All rights reserved.